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 10631 - Named access on the Window object doesn't work for XHTML documents in WebKit, Firefox, or (trivially) IE. Dumping objects in the global scope is sad face. Can we restrict this behavior to HTML documents? (The bug for implementing this in XHTML was rece
Summary: Named access on the Window object doesn't work for XHTML documents in WebKit,...
Status: RESOLVED NEEDSINFO
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: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-14 17:40 UTC by contributor
Modified: 2011-12-10 04:06 UTC (History)
8 users (show)

See Also:

Attachments

Description contributor 2010-09-14 17:40:17 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#named-access-on-the-window-object

Comment:
Named access on the Window object doesn't work for XHTML documents in WebKit,
Firefox, or (trivially) IE.  Dumping objects in the global scope is sad face. 
Can we restrict this behavior to HTML documents?  (The bug for implementing
this in XHTML was recently WONTFIXED in WebKit.)

Posted from: 67.169.42.39
Comment 1 Adam Barth 2010-09-14 17:42:37 UTC 
I'm told that Firefox restricts this to quirks mode, but I haven't verified that.
Comment 2 Ian 'Hixie' Hickson 2010-09-15 13:20:30 UTC 
Long term obviously the spec will spec whatever the browsers do, but short-term, it seems bad to encourage even more differences between HTML and XHTML or quirks mode and non-quirks mode (and even worse, to encourage differences in both simultaneously).

What do IE9 and Opera do?
Comment 3 Henri Sivonen 2010-09-15 13:33:06 UTC 
Making this a quirks/standards difference makes more sense than making this an HTML/XHTML difference, IMO. HTML Standards is the preferred mode, right?
Comment 4 Simon Pieters 2010-09-15 16:26:03 UTC 
Opera supports named access in HTML quirks, HTML standards and XHTML.

I'm a bit scared about removing it from HTML standards, since it is likely to break pages (either IE-only content (or even WebKit-only content) that breaks in Firefox today or content where Opera happens to get the IE codepath instead of the Firefox codepath).
Comment 5 Ian 'Hixie' Hickson 2010-09-28 22:38:44 UTC 
So WebKit makes this a MIME type difference, Gecko makes it a quirks mode difference, and Opera implements it everywhere.

What does IE9 do?
Comment 6 Ian 'Hixie' Hickson 2010-09-30 08:50:24 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: see comment 5 - I need more data to figure out where to go with this