- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Feb 2011 09:16:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11671 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |WONTFIX --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-16 09:16:44 UTC --- (In reply to comment #0) > > Section 4.10.7.1.14 (range state) > -Why doesn't the readonly attribute apply to the range state? Because only text fields have a concept of "readonly". UI widgets for range controls do not (they can be disabled, but not left interactive but readonly -- if you think about it, it makes no sense). > Section 4.10.7.1.15 (color state) > -It says "In this state, there is always a color picked, and there is no way to > set the value to the empty string." and "otherwise, set it to the string > "#000000"" > This may be problematic because I can't differ between no color has been set > and black. There's no way to not have a color set. It's like a checkbox, which is either checked or not, it can't not have a value at all, or a range control, whose pointer has to point somewhere, it can't just not have a value. > -Related to the above the required attribute does not apply to the color state. Right, it's impossible to not set a value, so it's not necessary to say it's required. > -Also in the color state the readonly attribute doesn't apply. Why? It's not a text field, same as with type=range. 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: see above. -- 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 Wednesday, 16 February 2011 09:16:46 UTC