- From: <bugzilla@jessica.w3.org>
- Date: Sat, 01 Jan 2011 05:33:22 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11360
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #7 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-01 05:33:20 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 only value you can see from .compatMode is "CSS1Compat". If you
ever find your document is in "quirks" mode or "limited quirks" mode, that
means your document is in some way non-conforming (e.g. you forgot your
DOCTYPE). The .compatMode feature is only specified for compatibility with
legacy content; there is, as far as I can tell, no use case for this feature in
practice. I highly recommend pretending that the .compatMode feature doesn't
exist.
I have therefore not made a change to the specification. I considered adding a
note, but I couldn't work out what a note would say that would be helpful. As
Ms2ger points out in earlier comments, the spec already seems to include all
the information you requested.
--
Configure bugmail: http://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 Saturday, 1 January 2011 05:33:23 UTC