HTML5 for today usage
is a proprietary syntax to give web browsers
a hint about documents that it should pre-fetch
because the user might visit them in the near future. (wiki)
What it does: Silently prefetching specified
documents to serve quickly.
- Inconsistent (Internet Draft Standard)
- Prefetch (moz) and prerender (webkit).
Usage: (eh hem, quite clear isn't it)
- Waste bandwidth (data plan)
- Web statistics
- Hidden security risks
Have problem looking for it on the Internet?
- Link Relations
- rel=first, last, next, prev, up
Expanded form options
Known as web form 2.0, due to the fact that it makes the form more interactive
Elements of the expanded options can even be styled.
Browsers' support: good overall support but incomplete (autocomplete, time, colorpicker, etc...). And for IE, that calls for polyfilling.
- Input type
- Validation (input type, required, regex, etc..)
- New elements (date pickers, sliders)
Customized (or customizable) input field for each data type (email, phone, colorpicker, etc...).
What it does: It is an easy way to include client-side validation. And then there're the smart phones.
Client-side validation in HTML is on by default, and turned off by "novalidate" attribute
But it isnt meant to replace server-side validation due to following reason...
Browsers' support: All browsers "support" HTML5 new input type. They may not do anything special with it but browsers that don’t recognize type="email" will treat it as type="text" and render it as a plain text field.
Issues: Browsers' support :)
Oh and lets not forget the list attribute - datalist which might be very useful in many case
Storing data the simple HTML5 way
The black art of location identification
Why a black art: Because its complicated, in terms of
- Old browsers support
- Gears! Warning: will no longer be available as of December 2012
- Error/Permission handling
Browsers' support: Surprisingly high, thanks to Gears and Geo.js
There are two other orignially-HTML5 features that I'm particularly interested: Web Worker and WebSocket. But they are both too complicated and hence deserve their own TechTalk and I am pretty sure I am not the best one around to talk about them.
Special thank to
- CanIUse.com for its illustrative support tables
- Mark Pilgrim and his outstanding HTML5 research and book
- Deck.js for facilitating this presentation
- And anyone out there working/blogging on/about HTML5