W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2010

[whatwg] Input color state: type mismatch

From: Mounir Lamouri <mounir.lamouri@gmail.com>
Date: Mon, 29 Mar 2010 10:58:07 +0200
Message-ID: <4BB06B9F.80409@gmail.com>
On 03/29/2010 10:38 AM, TAMURA, Kent wrote:
>> By the way, it looks like WebKit has implemented type mismatch for color
>> state [1] [2].
> 
> Yes.  That's because the type=color implementation of WebKit is just a
> text field for now.  Users can specify invalid strings.
> When we complete the implementation of dedicated UI and value
> sanitization, typeMismatch won't be true.

I understand this is because there is only a simple text field for now
but in a general matter, having typeMismatch for the color state would
be fine because the UI is optional and we can easily imagine UA not
adding an UI.
I was not saying WebKit did wrong but the opposite ;)

--
Mounir

> 
> 
> -- 
> TAMURA Kent
> Software Engineer, Google
> 
> 
> 
Received on Monday, 29 March 2010 01:58:07 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:22 UTC