My super-short post that attempts to answer this question as completely and accurately as possible in three presentation-friendly bullet points. HTML5 … re-imagines HTML as an API with objects, events, interfaces, and methods or a collection of interfaces. defines an algorithm for generating a consistent, cross-browser friendly DOM tree, regardless of the quality of the [...]
[26 Oct 2011]
To date, Firefox does not yet support the loop attribute of the <video> element. This snippet is a simple work-around. Once the video’s ended event is fired, it calls the play method. For more, consult the media events section of the HTML5 specification.
[4 Oct 2011]
One of the neat things about HTML5 is that it allows for multiple file uploads in one file upload field. Of course, you have to have a browser that supports such a feature. Currently Opera 11.10 does. So do Firefox 4, the latest version of Chrome, and Safari 5.0.4. (Internet Explorer 9 does not.) Now [...]
[29 Mar 2011]
… on non-void elements, at least. One of the big misconceptions about HTML5 is that any tag can be self-closed. That’s not true, though it appears that way. What HTML5 does is provide parsing rules for handling mismatched tags and markup. While it seems like self-closing tags are acceptable, that’s not the case. This post [...]
[23 Mar 2011]
Namespaces can be a great way to build up a pragmatic URL structure that’s easy to remember with continued usage. What do I mean by a namespace? I mean a portion of a URL that dictates unique content. One of Kyle Neath’s tips from his post URL design. This. URLs make your site more usable, [...]
[6 Jan 2011]
Today’s 24Ways entry is from Christian Heilmann and takes a look at HTML5 Local Storage. Heilmann explains: Why client-side storage can be a good thing; The origins of and need for local storage; How to use local storage; When to use local storage; I implemented local storage in browsers that support it for our wedding [...]
[7 Dec 2010]
The most important aspect of HTML5 isn’t the new stuff like video and canvas (which Safari and Firefox have both been shipping for years) it’s actually the honest-to-god promise of interoperability. Even stodgy old Microsoft, who has been doing their best to hold back the web for nearly a decade, understands this and you’ll see [...]
[12 Jul 2010]
In my first post on HTML5 video and its progress event, I wrote: Only Firefox provides a means to calculate the amount of the video that has been loaded. The progress event object includes total and loaded properties that reflect the total size of the video file, and the amount the browser has retrieved from [...]
[6 Jul 2010]
UPDATE: Thanks to zcorpan’s comments, I have posted a follow-up entry that should clarify the current status of the video element and its properties. I have been playing around with the HTML5 video interface lately, trying to understand what can be done with it, and how each browser supports its features as set forth in [...]
[5 Jul 2010]
We need to do more than just point the browser at a video file like the image tag does – there’s a lot more to it than just retrieving and displaying a video. The <video> tag certainly addresses the basic requirements and is making good progress on meeting others, but the <video> tag does not [...]
[30 Jun 2010]