W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2010

[Bug 9357] New: input element color state should be able to suffer from a type mismatch

From: <bugzilla@wiggum.w3.org>
Date: Sun, 28 Mar 2010 17:17:33 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9357-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9357

           Summary: input element color state should be able to suffer from
                    a type mismatch
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/spec/forms.html#color-state
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: mounir.lamouri@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


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


-- 
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, 28 March 2010 17:17:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 28 March 2010 17:17:41 GMT