[whatwg] Input color state: type mismatch

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 <ian at hixie.ch> wrote:

> 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.   `._.-(,_..'--(,_..'`-.;.'




-- 
TAMURA Kent
Software Engineer, Google




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100728/a8ccc17f/attachment.htm>

Received on Wednesday, 28 July 2010 07:28:50 UTC