W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[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

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Oct 2012 23:31:11 +0000
Message-Id: <E1TJBvj-0000IR-Nv@jessica.w3.org>
To: public-html-bugzilla@w3.org

Edward O'Connor <eoconnor@apple.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |eoconnor@apple.com
         Resolution|                            |NEEDSINFO
         AssignedTo|dave.null@w3.org            |eoconnor@apple.com

--- Comment #2 from Edward O'Connor <eoconnor@apple.com> 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:


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.

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 Tuesday, 2 October 2012 23:31:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:34 UTC