- From: <bugzilla@jessica.w3.org>
- Date: Sun, 08 May 2011 03:38:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12359 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |ian@hixie.ch Resolution| |WONTFIX --- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-05-08 03:38:00 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 already separates the UA requirements from the authoring conformance criteria — to make that distinction clear, toggle the switch at the top of the page to "Highlight browser rules". This spec is very carefully written so that you never have to read between the lines. It means exactly what it says and no more. If text says "When the pot contains an apple", it doesn't mean pots are allowed to contain apples. When it says "A pot must only contain an apple", it doesn't mean that software is allowed to give up if it contains something other than an apple. I could hand-hold the reader throughout the specification, but the thing is already 500+ pages long. It would become absolutely insufferable if it was that verbose. -- 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 Sunday, 8 May 2011 03:38:03 UTC