- From: <bugzilla@jessica.w3.org>
- Date: Sun, 26 Feb 2012 18:09:33 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16124
Summary: 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
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#nam
ed-access-on-the-window-object
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: other Hixie drafts (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org
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
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 26 February 2012 18:09:35 UTC