Per Ian Hixie -- the GOOGLE guru and father of HTML 5: Sending XHTML as text/html considered harmful In accordance with Mr. Hixie's current recommendation I am now using HTML 5 (just a little tongue-in-cheek here). Actually this is probably the way many web authors will begin to migrate their pages to HTML 5. James
I am wondering how many browsers support HTML 5. As soon as I know Firefox and related browser support it fully, I will begin coding in it. Another version to learn
Actually, Destinyx3, the tongue-in-cheek is that my HTML 5 (sig block) page is just a HTML 4.01 (strict) page with the HTML 5 Doctype and correct headers applied. Right now the page displays correctly in all current User-Agent versions (Graphical Browsers: MSIE 6 & 7; Firefox; Opera; Chrome; Safari) -- a good indication of current backward compatability. Of course, the big test for Browser rendering will come as new stable HTML 5 elements/attributes/constructs are introduced into the specification. James
Ah, James, you can see, nobody is listening to you, they just see that word "HTML5". Lawlz, I have one page using the doctype and the shortened meta tag and when I have my page checked by the webrichtlijnen.nl (which was obviously only built for HTML4 and XHTML1) it gets so confuzled. I thought that was funny. I probably won't be doing any "migrating". I'm not hip enough for that. If something comes along that requires any of the funkier stuff in HTML5, I'll prolly have to use it, otherwise not. I'm still leery of all the added behaviours in the HTML.. though someone pointed out to me it's along the same lines as the behaviour of an anchor being clicked as native to HTML as well... might have a point there.
Oh, that makes more sense. That's great then. I may have to start learning more when CSS3 becomes more browser-friendly.
i'll be excited to code pages for html 5 format whatwg.org is still busy with it i guess http://www.whatwg.org/specs/web-apps/current-work/multipage/