This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
For some reason I couldn't access the Editor's Draft, so this is off the November 16th Working Draft. A few thing I noticed while looking trough section 4.10.7: Section 4.10.7.1.14 (range state) -Why doesn't the readonly attribute apply to the range state? 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. -Related to the above the required attribute does not apply to the color state. This a problem when the problem above is addressed. However it may also be a problem when Javascript fallback is written for the form control and the validation. -Also in the color state the readonly attribute doesn't apply. Why?
(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.
mass-move component to LC1