16124 2012-02-26 18:09:33 +0000 Only recommending this be limited to quirks mode is not strict enough. This behaviour breaks page JS code in a way that makes it virtually impossible to find out why if(!objectname) is not resolving the way it should. This feature should be changed to "ma 2012-08-23 22:00:30 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#named-access-on-the-window-object P3 normal Unsorted 1 contributor ian ian mike Ms2ger contributor oldest_to_newest 64624 0 contributor 2012-02-26 18:09:33 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#named-access-on-the-window-object Complete: http://www.whatwg.org/c#named-access-on-the-window-object Comment: Only recommending this be limited to quirks mode is not strict enough. This behaviour breaks page JS code in a way that makes it virtually impossible to find out why if(!objectname) is not resolving the way it should. This feature should be changed to "may only be used in quirks mode", or better yet, should be removed from the spec, or changed to named access on document, because that's what window.document is for. Window pollution should be enough reason to flag this as a hack. Posted from: 173.206.22.96 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1 64977 1 Ms2ger 2012-03-03 20:26:43 +0000 I'm all for. Go convince browser vendors? 70633 2 contributor 2012-07-18 17:12:58 +0000 This bug was cloned to create bug 18082 as part of operation convergence. 71485 3 ian 2012-07-26 04:46:56 +0000 Yeah, what Ms2ger said. I can only change the spec here if the browser vendors are willing to change. 72660 4 ian 2012-08-23 22:00:30 +0000 Marking NEEDSINFO. The info I need is that the browsers have removed this.