Shows a color wheel or similar interface.

• UC does nothing: it doesn’t even show the keyboard.

<input list="ppk" name="list" />
<datalist id="ppk">
	<option label="ppk" value="ppk"></option>
	<option label="JavaScript" value="JavaScript"></option>
</datalist>

Shows the listed values as a suggestion/autocomplete box. Users can type in an alternative value, though.

• Works in Opera Mobile 10 (exactly as on desktop), but the calendar widgets are pretty hard to use, especially since you can’t zoom in on them.
• The widgets have been improved in Opera 11.5, but I can’t fill in a time. and the month and week types show the same widget as the date type.
• Nobody but Opera supports type="week".
• BlackBerry PlayBook 2 lost support for type="month"; something that OS6 supported fine.
• Firefox pops up the numeric keyboard but does not validate the results.
• UC does nothing: it doesn’t even show the keyboard.

Value is automatically validated as an email address, and if it’s invalid form submission is halted.

• Safari gives a customised keyboard but does not validate the field.
• PlayBook 2 dropped support.
• Firefox adds a red border around an input with an incorrect value, but doesn’t prevent the user from submitting it.

• Opera 10 gives a control, and that’s it.
• Opera 11.5 validates the content of the field, but only internally: no error message is shown.
• Android: Nexus One (2.3) pops up the numeric keyboard. HTC Legend (2.1) doesn’t.
• Android 3.2 pops up a numeric keyboard, but doesn’t allow any non-number characters such as - and e (for exponents) to be entered. Its validation is thus too strict.
• Obigo WebKit disallows characters (correctly), but does not automatically switch to the numeric keyboard.
• Firefox and Safari 3.2 pops up the numeric keyboard but do not validate the results.

Shows a slider. On touchscreen phones you have to tap; not slide. Except on iOS, where you first have to tap the slider button and then you can slide it. This interaction is not up to Apple’s usual high standards.

• Android 3.2 and UC don’t show any interface at all. Not even a default text box.

The spec says this type should do nothing special. Browsers assidiously comply. But some sort of validation would be possible here, right?

• Android: 2.3 and 3.2 pop up the numeric keyboard. HTC Legend (2.1) doesn’t.
• BlackBerry restricts input, but that’s it.
• Firefox and MeeGo pop up the numeric keyboard but do not validate the results.
• Safari gives a customised keyboard but does not validate the field.
• UC does nothing: it doesn’t even show the keyboard.

Value is automatically validated as a URL, and if it’s invalid form submission is halted.

Problem is: what is actually a URL? I’ve heard people say that quirksmode is a valid URL. I don’t like it for beans, but they could be right.

• Safari gives a customised keyboard but does not validate the field.
• PlayBook 2 dropped support.
• UC does nothing: it doesn’t even show the keyboard.
• Firefox adds a red border around an input with an incorrect value, but doesn’t prevent the user from submitting it.

<input type="text" autofocus>

The browser automatically focuses on this field when the page is loading but does not pop up the software keyboard. Actually this is the best possible implementation on pure touchscreen devices — if you want to implement it at all.

<input type="file" multiple>

Allows users to upload multiple files at once.

One problem on mobile is that the interface is not suited for selecting more than one file at a time.

<input pattern="[0-9]{4}[ ]?[A-Z]{2}" />

The value must conform to the regexp pattern, or submission is halted.

• PlayBook 2 dropped support.
• Firefox adds a red border around an input with an incorrect value, but doesn’t prevent the user from submitting it.

<input type="text" placeholder="Some text">

The placeholder text is shown as long as the field is unfocused and the user has not entered another value.

Firefox doesn’t allow use of the Backspace in form fields, so I cannot complete this test (removing value and seeing if placeholder reappears).

<input type="number" readonly>

User cannot enter a value in the form field.

<input type="text" required>

Form submission is halted if a required field does not have a value.

• PlayBook 2 dropped support.

• Field controls in Opera 10 are too small; I can’t click on them. They’re there, though.
• PlayBook 2 dropped support.