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 18082 - 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
Summary: Only recommending this be limited to quirks mode is not strict enough. This b...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:12 UTC by contributor
Modified: 2012-10-02 23:31 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2012-07-18 17:12:55 UTC 
This was was cloned from bug 16124 as part of operation convergence.
Originally filed: 2012-02-26 18:09:00 +0000

================================================================================
 #0   contributor@whatwg.org                          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
================================================================================
 #1   Ms2ger                                          2012-03-03 20:26:43 +0000 
--------------------------------------------------------------------------------
I'm all for. Go convince browser vendors?
================================================================================
Comment 1 Ms2ger 2012-08-15 17:13:24 UTC 
Filter on [Idon'tcareaboutHTMLWGbugspam].
Comment 2 Edward O'Connor 2012-10-02 23:31:11 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: No spec change.
Rationale: The spec is the way it is because it matches browser
behavior. If you're able to convince browser vendors to change their
engines, we could consider changing the spec.