"Catching up" is easy. My HTML5 usage can be summarized as follow:
- HTML5 doctype
- Usage of HTML5 new semantic elements (header, footer, aside, figure, etc). Don't forget to include the html5shiv so that IE < 9 can style these new elements in CSS
- Some basic HTML5 form properties, such as the placeholder attribute and new input types (for example "email").
All of this is just a slight variation of what you are already doing. You can start using it in your next project and it will work in all browsers.
Don't wait for HTML5 to be completed. It never will. In fact, it doesn't exist anymore. It is simply "HTML" now and defined as a "living" standard. All you need to do is handpick what is safe to use for your audience. In the odd case that you find yourself in love with an unsafe feature, visit this page that collects all fallbacks known to man:
"Catching up" is easy. My HTML5 usage can be summarized as follow:
- HTML5 doctype
- Usage of HTML5 new semantic elements (header, footer, aside, figure, etc). Don't forget to include the html5shiv so that IE < 9 can style these new elements in CSS
- Some basic HTML5 form properties, such as the placeholder attribute and new input types (for example "email").
All of this is just a slight variation of what you are already doing. You can start using it in your next project and it will work in all browsers.
Don't wait for HTML5 to be completed. It never will. In fact, it doesn't exist anymore. It is simply "HTML" now and defined as a "living" standard. All you need to do is handpick what is safe to use for your audience. In the odd case that you find yourself in love with an unsafe feature, visit this page that collects all fallbacks known to man:
https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills
In return of this awesome advise, all who read this must now join JungleDragon:
http://www.jungledragon.com/join
I figure that if this blog entry is about promoting me, I might as well go all the way :)