It was announced on the HTML Working Group mailing list this morning that the font element will be absent from the next draft of the HTML5 specification. The inclusion of font in the spec was controversial, as many (including myself) thought it was a purely decorative element that had no place in semantic code.
Of course, browsers will still have to support the element because of the many legacy sites on the web; but as of now any software that generates mark-up should use the style attribute instead. It’s a small increment better.
After two days of commotion regarding the Internet Explorer team’s decision to include a standards opt-in in the next version of their browser, Mozilla’s John Resig has noticed something rather important in an exchange on IE’s Chris Wilson’s blog; namely:
Internet Explorer 8 will support DOCTYPE switching for new DOCTYPEs (like HTML5).
Read the full article
There’s an interesting post on warpspire.com at the moment, decrying the speed of implementation for HTML 5 and CSS 3 and suggesting Flash/AIR as a better alternative. I completely disagree with it, but it’s interesting nonetheless. HTML 5 in particular comes in for heavy criticism as it’s perceived that its adoption will take too long.
But, as the title of this post makes clear: you can start using HTML 5 right now!
Well, you can’t really – but with Opera and Safari, you can at least pretend to while you get used to the syntax.
Read the full article
I’ve been doing a bit of thinking recently.
I’ve been thinking about HTML 5 and the new semantic sectioning elements it proposes to introduce: header, footer, section, article, nav and aside.
I’ve also been thinking about the way microformats use data format standards and reserved class and id values to organise content.
Then thinking about this 2005 research into reused class names, which shows that, probably mostly unconsciously, website makers were already using the proposed HTML 5 elements as class names to organise their data.
Read the full article
Firefox has experimental support. Opera has experimental support. And now, Webkit has experimental support. The new HTML5 <video> element is getting support from a large part of the browser market.
According to the spec, User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format
; Firefox and Opera do so natively, while Webkit does so with a plugin for Quicktime (see Xiph.org).
According to my site stats – which are very far from being representative – roughly 60% of my visitors use one of the three browsers mentioned above; that’s a pretty big potential market. And remember, what the geeks use now, everybody will use in a year or two.