[whatwg] Input color state: type mismatch

Ian Hickson ian at hixie.ch
Tue Jul 27 16:45:16 PDT 2010


On Mon, 5 Apr 2010, TAMURA, Kent wrote:
> On Sat, Apr 3, 2010 at 06:37, Ian Hickson <ian at 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 point number.
> > 
> > The user agent shouldn't update the value until the input is a valid 
> > number. ("User agents must not allow the user to set the value to a 
> > string that is not a valid floating point number.")
> 
> Why are type=email and url different from type=number at this point?

Mostly because numbers are simpler, so it seemed less useful to expose 
half-entered numbers to the script. However, if people disagree with this 
I'm happy to change it so that those three work the same.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'


More information about the whatwg mailing list