I’ve been searching this online and I can’t seem to find a definitive answer (mostly surrounding IE7/8…don’t care about 6 anymore).
Well to begin with google use html5 (badly) on their home page.
From what I understand it’s not going to make much difference at the moment, <h1>’s are still <h1>’s, <h2>’s are still <h2>’s and links are still links etc. But looking forward, as it becomes more of the norm (microsoft take note!) I believe it can only help as the search engines learn to classify the content they find based on the new tags surrounding it.
thats a good point, i mean its ultimately only divs and indescript things being replaced,
very turned on by HTML5 at least the core basic new tags seems like the are supported, gonna check out those links you posted earlier.. I think they were down at the time, or my internet was just doing what it does best (not working)
I was about to make a similar post, but decided to bump this back up.
Is anyone using HTML5 on a regular basis, and if so, have you discovered any issues? I’m planning on switching from XHTML 1.0 strict to HTML5 and was just wondering if there was anything I need to keep in mind as far as cross-browser compatibility / implementing jQuery stuff / PHP includes, etc…
I’ve been using it over at my site and it’s been fine. I know the guys at Carsonified (http://carsonified.com/) use it and many more do too.
…which then turns those elements into block elements. I’ve made a demo page here (http://www.jamesduncombe.com/html5/) which demo’s CSS3 and HTML5 (it works in Safai/Chrome and FF). If you have a look at the source it will show you the elements I used. The HTML is clean but the CSS is very messy at the moment (I had a bet with someone about keeping it tiny!).
Hope that helps,
The thing to remember is that HTML5 isn’t ratified yet. What does this mean for you? Well if you produce an XHTML 1.0 compliant website it will remain compliant forever. This is important if you are doing client facing work as opposed to internal projects or sites that are updated frequently (like the Google homepage). I like to validate my sites before I hand them over to a client and know it’s not going to break at some point in the future. Bear in mind that any HTML5 sites that you produce today may end up invalid once the standard has been finalised.
Another point to consider is whether you need any of the new HTML5 features (i.e. Canvas, forms, offline storage, etc). If not then what is your reason for switching – is it just that it’s the "cool" thing to do? Renaming <div> to <content> is nice, but… it’s just not enough of a win for me at the moment.
Unless you need one or more of the new features, it’s not time for HTML5 yet. Feel free to experiment, and go ahead if you absolutely must be in the "cool" crowd.
You must be logged in to reply to this topic.