Re: [whatwg] Input color state: type mismatch

2010-07-28 Thread TAMURA, Kent
Please see http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-July/027243.html In short words, I disagree with the current spec. On Wed, Jul 28, 2010 at 08:45, Ian Hickson i...@hixie.ch wrote: On Mon, 5 Apr 2010, TAMURA, Kent wrote: On Sat, Apr 3, 2010 at 06:37, Ian Hickson

Re: [whatwg] Input color state: type mismatch

2010-07-27 Thread Ian Hickson
On Mon, 5 Apr 2010, TAMURA, Kent wrote: On Sat, Apr 3, 2010 at 06:37, Ian Hickson i...@hixie.ch wrote: On Sat, 3 Apr 2010, TAMURA, Kent wrote: I found type=number also had no typeMismatch. If a user wants to type a negative value, he types '-' first. �This state should make

Re: [whatwg] Input color state: type mismatch

2010-04-04 Thread TAMURA, Kent
On Sat, Apr 3, 2010 at 06:37, Ian Hickson i...@hixie.ch wrote: On Sat, 3 Apr 2010, TAMURA, Kent wrote: I found type=number also had no typeMismatch. If a user wants to type a negative value, he types '-' first.  This state should make typeMismatch true because '-' is not a valid floating

Re: [whatwg] Input color state: type mismatch

2010-04-02 Thread TAMURA, Kent
I found type=number also had no typeMismatch. If a user wants to type a negative value, he types '-' first. This state should make typeMismatch true because '-' is not a valid floating point number. -- TAMURA Kent Software Engineer, Google

Re: [whatwg] Input color state: type mismatch

2010-04-02 Thread Ian Hickson
On Sat, 3 Apr 2010, TAMURA, Kent wrote: I found type=number also had no typeMismatch. If a user wants to type a negative value, he types '-' first. This state should make typeMismatch true because '-' is not a valid floating point number. The user agent shouldn't update the value until the

Re: [whatwg] Input color state: type mismatch

2010-03-29 Thread TAMURA, Kent
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,

Re: [whatwg] Input color state: type mismatch

2010-03-29 Thread Mounir Lamouri
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

Re: [whatwg] Input color state: type mismatch

2010-03-29 Thread Aryeh Gregor
On Sat, Mar 27, 2010 at 9:48 AM, Mounir Lamouri mounir.lamo...@gmail.com wrote: It looks like the input color state can't suffer from type mismatch according to the specs but it seems to be the only way to be sure the value is correct. Email and URL states can suffer from type mismatch for the

Re: [whatwg] Input color state: type mismatch

2010-03-29 Thread Mounir Lamouri
On 03/29/2010 09:49 PM, Aryeh Gregor wrote: On Sat, Mar 27, 2010 at 9:48 AM, Mounir Lamouri mounir.lamo...@gmail.com wrote: It looks like the input color state can't suffer from type mismatch according to the specs but it seems to be the only way to be sure the value is correct. Email and URL