10631 2010-09-14 17:40:17 +0000 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 2011-12-10 04:06:31 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO https://bugs.webkit.org/show_bug.cgi?id=22211 http://www.whatwg.org/specs/web-apps/current-work/#named-access-on-the-window-object P3 normal --- 1 contributor ian cam ddkilzer hsivonen ian mike public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 39018 0 contributor 2010-09-14 17:40:17 +0000 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 39019 1 w3c 2010-09-14 17:42:37 +0000 I'm told that Firefox restricts this to quirks mode, but I haven't verified that. 39052 2 ian 2010-09-15 13:20:30 +0000 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? 39054 3 hsivonen 2010-09-15 13:33:06 +0000 Making this a quirks/standards difference makes more sense than making this an HTML/XHTML difference, IMO. HTML Standards is the preferred mode, right? 39061 4 zcorpan 2010-09-15 16:26:03 +0000 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). 39821 5 ian 2010-09-28 22:38:44 +0000 So WebKit makes this a MIME type difference, Gecko makes it a quirks mode difference, and Opera implements it everywhere. What does IE9 do? 40101 6 ian 2010-09-30 08:50:24 +0000 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