[whatwg] Input color state: type mismatch
tkent at chromium.org
Sun Apr 4 19:19:17 PDT 2010
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?
Software Engineer, Google
More information about the whatwg