This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9726 - Spec the features argument
Summary: Spec the features argument
Status: CLOSED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: Disagree, NE
Depends on:
Blocks:
 
Reported: 2010-05-13 12:32 UTC by contributor
Modified: 2010-10-04 14:29 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2010-05-13 12:32:24 UTC
Section: http://www.whatwg.org/specs/web-apps/current-work/#dom-open

Comment:
Spec the features argumen

Posted from: 91.181.137.76 by ms2ger@gmail.com
Comment 1 Ian 'Hixie' Hickson 2010-09-10 09:02:03 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: It is specced — user agents are entirely allowed to ignore it, and are not disallowed from doing anything they want with it.

Are there any particular features of this argument that you think should be specified in more detail? If so, which? And why?
Comment 2 Ms2ger 2010-09-12 14:27:42 UTC
That should be made clearer. In particular, "The third argument, /features/, has no effect…" is wrong.

I don't know a lot about window.open, but from what I remember from reading the source, it seems at least parsing the string is very compat-sensitive.
Comment 3 Ian 'Hixie' Hickson 2010-09-28 06:26:16 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: see diff below
Rationale: I've changed the text to be more accurate, but haven't specced anything new. If you want something specced, tell me what it is exactly what why interop for that feature matters.
Comment 4 contributor 2010-09-28 06:26:41 UTC
Checked in as WHATWG revision r5525.
Check-in comment: Change how we ignore window.open()'s third argument.
http://html5.org/tools/web-apps-tracker?from=5524&to=5525