Offers the user a customised interface (custom keyboard on touchscreen; arrows on desktop)

Restricts input to numbers (and related characters such as a negative sign)

Does not send incorrect data to the server

Halts form submission upon finding incorrect data

Informs the user of a failed submission with an error message

Safari offers the numeric keyboard, but allows the user to switch to the alphabetic one and doesn’t validate the data.
This is all the weirder since the iPhone, at least, has a fully numeric keyboard (it’s used for tel.

Android 2 also offers the numeric keyboard, and refuses to allow the user to enter other characters in the input field.

Chromia show the numeric keyboard, except Puffin, which shows the general one. However, Puffin gives an error message when the value is not numeric.

UC on Huawei offers the numeric part of the regular keyboard and nothing else. The ones on Xiaomi and S4 do this correctly.

BB6/7, which have a physical keyboard, only accept keys that can have a numeric value. The others are ignored.

Opera Classic allows any input but doesn’t send non-numeric values to the server. It doesn’t show any error message.

The browser automatically focuses on this field when the page is loading. Whether that is a good idea on mobile is an open question. Users may not liked being yanked to a different part of the page because of an autofocus.

BB6/7 supports it fully, and that’s OK, since it has a hardware keyboard.

Firefox Android supports it fully and thus opens the keyboard when the user enters the page. Wrong decision.

A perfectly-supporting browser would present the date picker interface and only allow you to pick dates that fall between
min and max. Among others, BlackBerry 6 and the Google and HTC Chromia do this.

Surprisingly, the Chromium-based browsers don’t support it; that is, the device doesn’t allow me to select multiple files. This could be a device failure, I suppose, instead of a browser failure. The net result is the same, though.

The app I use for WebView testing does not support selecting files at all.

I test this attribute by entering 11, which is a wrong value. The browser is supposed to reject it and inform the user of that fact.

Minimal

Wrong values are not sent to the server, but the user isn’t notified of an error, either.

LG and Opera Chromium don’t send the offending value to the server, but don’t show an error message, either.

UC halts form submission but does not give an error message.

If you set step="3" and enter 11 in the field and submits the form, the following happens:

IE tells the user to enter a valid value but doesn’t tell the user what a valid value looks like.

Firefox and the Chrome-based browsers show an error message with the closest legal values.

iOS

iOS WebView

And. 4

AWK WebView

Chromium

Chromium WebView

UC

BlackBerry

Nokia Xpress

UC Mini

Opera

Nintendo

Dolphin

IE

Firefox

7

8

7

8

Sa

Puf

LG

Cy

HTC

Xia

Op

Go

30

33

37

9

10

6

7

10

Mini

Classic

9

10

11

And

OS

Android WebKit 4

Android WebKit 4 is such a mess that it needs its own, private compatibility table for some types. The columns below are for default browser and WebView both, except for Huawei and LG, where the WebView can’t be tested, and Xiaomi, which has a Chromium-based default browser.

Wolfgang AT-AS45FW note: Wolfgang is a Dutch importer and re-brander of phones. In this particular case
they seem to have bought Chinese (? probably) phones, re-branded them, then re-sold them to the Whoop company, which
re-branded them and sold them to the Hema chain of supermarkets, which sells them to consumers as the Whoop Echo. Supply chain management FTW!