Authors should not, but may despite requirements to the contrary elsewhere in this specification, specify the maxlength and size attributes on input elements whose type attributes are in the Number state. One valid reason for using these attributes regardless is to help legacy user agents that do not support input elements with type="number" to still render the text control with a useful width.

I'm not entirely sure I understand the rationale. Size is something different than min/max (or its regular input equivalent maxlength). Presumably it has something to do with this:

The type=number state is not appropriate for input that happens to only consist of numbers but isn’t strictly speaking a number. For example, it would be inappropriate for credit card numbers or US postal codes. A simple way of determining whether to use type=number is to consider whether it would make sense for the input control to have a spinbox interface (e.g., with "up" and "down" arrows). Getting a credit card number wrong by 1 in the last digit isn’t a minor mistake, it’s as wrong as getting every digit incorrect. So it would not make sense for the user to select a credit card number using "up" and "down" buttons. When a spinbox interface is not appropriate, type=text is probably the right choice (possibly with a pattern attribute).

CharlesEF wrote:Oh, since other browsers support the re-size but Firefox doesn't I have to use CSS instead. I mean, even IE 11 and Edge support this but Firefox doesn't!

Chromia and WebKits seem to behave the same as Firefox so "other browsers" really just means one browser.

(Edge is IE12 no matter what they call it.)

Intelligent alien life does exist, otherwise they would have contacted us.