In the first article in this series we looked at the history of HTML5 forms and many of the new attributes available to us. In this second and final part of the series, we’ll look at the new input types available in HTML5. As we’ll see, these new features will go a long way toward making your life easier while delivering a delightful user experience. The best thing about all this? You can start using them now.
This is article is an excerpt from Chapter 6 of Beginning HTML5 and CSS3: The Web Evolved by Christopher Murphy, Oli Studholme, Richard Clark and Divya Manian, published by Apress.
Note: As this article is a book excerpt, browser renderings of attributes and input types may have altered since the screenshots were taken. Additionally, browser support may have increased since publication so please refer to the links at the end of the article for the current state of browser support.
New input types
HTML5 introduces no less than a baker’s dozen (yes, that’s 13!) new input types for forms. We’re going to take a brief look at each of them and explain why you should be using them right now. These new input types have dual benefits: using them means less development time and an improved user experience. The new input types we’ll be looking at are:
Search seems like an appropriate place to start our foray into HTML5 input types. When we talk about search, we’re not just talking about Google, Bing, or Yahoo. We’re talking about the search field on that e-commerce site you just made a purchase from, on Wikipedia, and even on your personal blog. It’s probably the most common action performed on the Web every day, yet it’s not marked up very semantically, is it? We all tend to write something like this:
<input type="text" name="search">
Well, what if we could write something like …
<input type="search" name="search">
With HTML5 we can. Feels much better, doesn’t it? Desktop browsers will render this in a similar way to a standard text field—until you start typing, that is. At this point, a small cross appears on the right side of the field. Notice the x in Figure 1. This lets you quickly clear the field, just like Safari’s built-in search field.
On a mobile device, however, things start to get interesting. Take the example iPhone shown in Figure 2; when you focus on an input using
, notice the keyboard, specifically the action button on the keyboard (bottom right). Did you spot that it says “Search” rather than the regular “Go”? It’s a subtle difference that most users won’t even notice, but those who do will afford themselves a wry smile.
As you’ve seen with the new attributes, browsers that don’t understand them will simply degrade gracefully. The same applies to all of the new input types discussed here. If a browser doesn’t understand
, it will default to
. This means you’re not losing anything. In fact, you’re using progressive enhancement and helping users to have a better experience. Let’s face it: filling out web forms isn’t very fun, so anything you can add to ensure a smoother experience, the better.
In rendering terms, the email input type is no different than a standard text input type and allows for one or more e-mail addresses to be entered. Combined with the
attribute, the browser is then able to look for patterns to ensure a valid e-mail address has been entered. Naturally, this checking is rudimentary, perhaps looking for an @ character or a period (.) and not allowing spaces. Opera 9.5+, Firefox 4+, Internet Explorer 10 and Chrome 5+ have already implemented this basic validation. The browser goes as far as presenting the user with an error message (see Opera in Figure 3) if the e-mail address entered isn’t valid. You can style the field for when an value is entered using the
pseudo class (assuming you have the required attribute on the input) just like Locum Dr. Peter explained.
<input type="email" name="email" required>
The specification details that one or more e-mail addresses are allowed. This means that the multiple attribute could be used with
There’s always a catch, though, right? At the time of writing, there is an internationalization issue with
. When using it with double-byte internationalized domain names, the browsers invalidate them; so this example
<input type="email" name="email" value="[email protected]日本.jp">
isn’t valid in Firefox, Safari, or Chrome (there is no issue in Opera). However, a workaround has been created by Kyle Barrow that uses
attribute, as shown here:
<input type="text" name="email" value="[email protected]日本.jp"pattern="[^ @]*@[^ @]*">
An alternative solution is to continue using
attribute on the submit button, as follows. This ensures that no validation will be carried out on form submission, which may or may not be suitable for your needs.
<form action="process.php"> <label for="email">Email:</label> <input type="email" name="email" value="[email protected]日本.jp"> <input type="submit" formnovalidate value="Submit"> Or you could use the novalidate attribute on your form, like so: <form action="process.php" novalidate> <labelfor="email">Email:</label> <input type="email" name="email" value="[email protected]日本.jp"> <input type="submit" value="Submit">
Internationalization issues aside, remember how we said there are dual benefits to HTML5′s input types—less development time and better user experience? Let’s go back and look at the iPhone once more, as shown in Figure 4.
Did you notice it this time? No? Look at the keyboard again. That’s right, the keyboard is different. There are dedicated keys for the @ and . characters to help you complete the field more efficiently. As we discussed with
, there is no downside to using
right now. If a browser doesn’t support it, it will degrade to
. And in some browsers, users will get a helping hand.
input type, as you might expect, is for web addresses. You can use the
attribute to enter more than one URL. Like
, a browser will carry out simple validation on these fields and present an error message on form submission. This is likely to include looking for forward slashes, periods, and spaces, and possibly detecting a valid top-level domain (such as .com or .co.uk). Use the
input type like so:
<input type="url" name="url" required>
Again, we’ll take a look at how the iPhone renders
. As you can see in Figure 5, it has again updated the onscreen keyboard to ensure that completing the field is as simple as possible for the user by swapping the default space key for period, forward slash, and .com keys. (To access more endings like .org and .net, tap and hold the .com key.)
in that no particular syntax is enforced. Phone numbers differ around the world, making it difficult to guarantee any type of specific notation except for allowing only numbers and perhaps a + symbol to be entered. It’s possible that you can validate specific phone numbers (if you can guarantee the format) using client-side validation.
is marked up as follows:
<input type="tel" name="tel" id="tel" required>
Once more, the iPhone recognises
, only this time it goes one step further and completely changes the keyboard to the standard phone keyboard, as shown on the left in Figure 6. In addition to the iPhone, some Android devices (such as HTC Desire, shown on the right in Figure 6) also display a numeric keyboard for
. That’s pretty handy, don’t you think? Nice, big keys for entering a phone number help you to get that big, nasty form completed quickly.
, as you might expect, is used for specifying a numerical value. As with the majority of these new input types, Opera was the first to implement
. It, Safari, and Chrome render the input as a spinbox control (see Figure 7) whereby you can click the arrows to move up or down. Or if you prefer, you can type directly into the field. Firefox, on the other hand, renders the field like a standard text box. Support for type=”number” is in IE 10 also, although if you enter a non-numerical character the field empties when focus is lost and no feedback is provided to the user.
With the additional attributes
we can change the default step value of this spinbox control as well as set minimum, maximum, and starting values (using the standard HTML
attribute). This example shows how these attributes work:
<input type="number" min="5" max="18" step="0.5"value="9" name="shoe-size">
In this example, min represents the minimum value the field will accept, and max represents the maximum value. If we reach the maximum or minimum value, the appropriate arrow on the spinbox control will be greyed out so you can no longer interact with it. step is the increment that the value should adjust up or down, with the default step value being 1. This means we can include negative values or step up in increments of 0.5 or 5. value is that attribute you’re used to from previous versions of HTML. Each of the attributes are optional, with defaults being set if they aren’t used.
In contrast to Opera’s implementation, the iPhone (Figure 8) and some Android devices (such as HTC Desire, shown on the right in Figure 6-13) simply render the field as a standard text box but optimize the keyboard for easy input.
To make the iPhone render with the standard telephone keypad as we saw for
Chris Coyier, of CSS Tricks devised a little hoax you can use. Rather than using type=”number”, use a standard
input and add a pattern attribute that accepts only numbers, as shown below. This solution isn’t ideal but if you think it could be useful, Chris has put a short video together showing it in action.
<input type="text" pattern="[0-9]*" name="shoe-size">
Chris’ technique may soon become absolete though with the introduction of the
attribute. The attribute, recently added to the specification will allow users to specify the type of input mechanism that is most useful for users. When implemented, you will be able to choose between numeric, latin, email, or kana input modes.
input type is similar to number but more specific. It represents a numerical value within a given range. Why the difference, I hear you cry? Because when you’re using
, the exact value isn’t important. It also allows browsers to offer a simpler control than for
. In Opera, Safari, Internet Explorer 10 and Chrome,
renders as a slider (see Figure 6-14). When moving the slider in IE 10 a tooltip appears showing the current value. Additionally, in Opera, if the CSS defines the height greater than the width, the slider control will be rendered vertically as opposed to the standard horizontal rendering.
The following code shows how we might mark up our skill level on a scale of 1 to 100 by setting the
attributes (see Figure 9). We can also set the starting point for
<input id="skill" type="range" min="1" max="100"value="0">
Dates and times
<input id="dob" name="dob" type="date">
You can go a step further by using the
attributes to ensure the user can only choose from a specified date range.
<input id="startdate" name="startdate" min="2012-01-01"max="2013-01-01" type="date">
As with many of the other form implementations, Opera leads the way (support in other browsers is varied). Let’s take a look next at how browsers render these input types.
Figure 10 shows Opera 10.5′s rendering of
These date pickers aren’t restricted to desktop devices; some Blackberry devices and Chrome for Android render its internal date picker when used with
(see Figure 11).
Next up, Figure 12 shows
, which might, for example, be used for a credit card expiry date.
<input id="expiry" name="expiry" type="month" required>
You can also drill down to
. Notice how Opera highlights a specific week using the same date picker control, as shown in Figure 13.
<input id="vacation" name="vacation" type="week">
You can see in Figure 14 that
renders a spinbox similar to that used earlier for selecting the precise time.
<input id="exit-time" name="exit-time" type="time">
We can combine the date and time by using
for specifying a precise time on a given day, as shown in Figure 15.
<input id="entry-day-time" name="entry-day-time"type="datetime">
Finally, Figure 16 shows that we can achieve slightly more granular control by selecting a precise time on a given day with a local time zone variation using
<input id="arrival-time" name="arrival-time "type="datetime-local">
Date and time caveats
There are two caveats with these implementations. First, with the current implementation, it isn’t possible to type a date into the field (in all browsers). The date picker is keyboard accessible, though. However, we can foresee a potential issue; if implemented on a form that a data entry clerk regularly completes, they are likely to be quicker at typing the date than tabbing through with the keyboard or selecting from a date picker. Second, it isn’t possible to style the look of the date picker. We tend to think that this is a good thing, as users will receive a common experience across all websites they visit (provided they use the same browser all the time). Undoubtedly, though, corporations will require a branded date picker. Safari 5 and Chrome 5 have implemented these input types, but, unfortunately, they aren’t very user friendly. Dates have to be entered in the same format as the time element that we met earlier in the book. So for dates, the format would be YYYY-MM-DD, and for dates with time, a user would have to enter YYYYMM-DDT00:00Z, which is not very friendly at all.
As with the other new input types, if a browser doesn’t recognize them, it will simply default back to
The color input type is pretty self-explanatory: it allows the user to select a color and returns the hex value for that color. It is anticipated that users will either be able to type the value or select from a color picker, which will either be native to the operating system or a browser’s own implementation. Opera 11 has implemented type=”color” with a simple color picker that offers a number of standard color choices or the option to select Other, which brings up the operating system color picker (shown on the right in Figure 17).
<input id="color" name="color" type="color">
In contrast, certain Blackberry devices have implemented the
input type that renders a color picker, as shown in Figure 18.
Input types summary
You can find a dummy form, using some of the examples we’ve shown in this article at our HTML5 forms demo page.
We’ve hinted throughout the article at which browsers have support for HTML5 forms input types and attributes. With new versions of browsers being released at an ever-increasing rate, it can be difficult to keep up with what is or isn’t supported. If you want to keep an eye on the current progress, we suggest visiting When can I use … orFindMeByIP or Wufoo’s HTML5 forms research.
If you missed the first article in this series on HTML5 forms, why not read a brief History of HTML5 forms and learn all about the new attributes introduced.