I’ve just finished reading Html5 for web designers by Jeremy Keith and would really recommend it. It’s not too big, I managed to finish it in 4 train journeys and I’m a slug when it comes to reading speed.
If you subscribe to Jeremy’s journal you’ll be familiar with his very laid back and personal writing style, injecting a welcome amount of wit to break up the reading.
I wasn’t quite aware of the relationship between the W3C and the WHATWG. It’s very interesting to see how the HTML5 spec is being put together. And now I actually understand what they are talking about when they refer to “paving the cowpaths”. It essentially is the mindset that if something already exists and it’s use is widespread then make it part of the spec (event if there is a better solution) and outline exactly how we should be using it consistently. The more I think over this the more I like it, “If it ain’t broke, don’t fix it” as Jeremy puts it.
A few highlights have got to be:
Web Forms 2.0
There are several new features which Jeremy goes in to, I’ve been looking at a few of these previously but it’s great seeing them side by side.
New input types
These all fall back to text inputs for older browsers.
<label for="email">Email address</label> <input id="email" name="email" type="email"> <label for="website">Website</label><input id="website" name="website" type="url"> <label for="phone">Telephone</label><input id="phone" name="phone" type="tel">
Validation and Error Handling
There is built in support for validating form input client side. For example:
<label for="pass">Your password</label> <input id="pass" name="pass" type="password" required>
Being able to write more modular markup with each structural
element having it’s own heading scope like so:
<h1>My Website</h1> <section> <h1>My section title</h1> <p>My section content</p> </section>
The best thing is this:
You can just swap your current doctype without a worry and start using this stuff!
You can find out more on the Book apart website