This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9357 - input element color state should be able to suffer from a type mismatch
Summary: input element color state should be able to suffer from a type mismatch
Status: CLOSED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/forms.ht...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-28 17:17 UTC by Mounir Lamouri
Modified: 2010-10-04 14:31 UTC (History)
5 users (show)

See Also:


Attachments

Description Mounir Lamouri 2010-03-28 17:17:33 UTC
At the moment, input elements in email and url states may suffer from a type mismatch if the value doesn't feed the need (ie. is not an email/url). When an input element is in the telephone state, it can't suffer from a type mismatch but the reason is explicitly mentioned.

However, input elements in color state have to follow a specific pattern for its value but the correctness of the value can't be checked. I think an input element in the color state should be able to suffer from type mismatch.

By the way, it looks like WebKit has already implemented type mismatch for color
state [1] [2].

[1] https://bugs.webkit.org/show_bug.cgi?id=28966
[2] https://bugs.webkit.org/attachment.cgi?id=39044
Comment 1 Ian 'Hixie' Hickson 2010-04-02 06:56:19 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: It's impossible for a color picker to be in a type mismatch state because the user agent is required to prevent the user from ever entering such a state. If WebKit's implementation can be in such a state then it is buggy.