Joe, thanks for analyzing the issue in more depth. As @annevk pointed out on a different communication channel, [the part of the spec we've been looking at](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#validity-states) is non-normative: ```(The definitions below are non-normative; other parts of this specification define more precisely when each state applies or does not.)``` In this case, [the constraint validation of `<input type="number">` covers this](https://html.spec.whatwg.org/multipage/input.html#number-state-(type=number)): ```Constraint validation: While the user interface describes input that the user agent cannot convert to a valid floating-point number, the control is suffering from bad input. ``` Changing `typeMismatch` nowadays seems impossible, because it would be a breaking change and apparently this has been specified already for a decade.
Bug 1574160 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Joe, thanks for analyzing the issue in more depth. As @annevk pointed out on a different communication channel, [the part of the spec we've been looking at](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#validity-states) is non-normative: ```(The definitions below are non-normative; other parts of this specification define more precisely when each state applies or does not.)``` In this case, [the constraint validation of `<input type="number">` covers this](https://html.spec.whatwg.org/multipage/input.html#number-state-(type=number)): ```Constraint validation: While the user interface describes input that the user agent cannot convert to a valid floating-point number, the control is suffering from bad input. ``` Changing `typeMismatch` nowadays seems impossible, because it would be a breaking change and apparently this has been specified already for a decade. I'll close the bug. Feel free to reopen it if I missed something.