Please leave your sense of logic at the door, thanks!

This Week in HTML5 – Episode 38

by Mark Pilgrim, Google in Weekly Review

Welcome back to "This Week in HTML 5," where I'll try to summarize the major activity in the ongoing standards process in the WHATWG and W3C HTML Working Group.

This week, there were some more refinements to microdata. r4139 changes the names of the DOM properties that reflect microdata markup. r4140 renames the content property to itemValue Since no browser has actually implemented this API yet, these changes shouldn't make any difference. Standards are like sex; one mistake, and you're stuck supporting it forever! r4141 and r4147 fix up some microdata examples, in particular this example from Gavin Carothers about marking up O'Reilly's book catalog. Hooray for real-world examples!

There were also some noteworthy changes to the <video> and <audio> API. r4131 says that setting the src attribute on one of those elements should call its load() method. r4132 removes the load event for multimedia elements, and r4133 removes the "in progress" events (loadstart, loadend, and progress) that used to be fired while the video/audio file was downloading.

Other noteworthy changes this week:

Around the web:

Tune in next week for another exciting edition of "This Week in HTML5."

5 Responses to “This Week in HTML5 – Episode 38”

  1. Too bad the firehose is too much to swallow – had I known about the discussion, I would have explained that if I did goad sayrer into supporting feed, it would have been because it provided an out for people whose feed was neither of the autodiscovery types (particularly, application/rdf+xml), without needing what the comment called our “really slimy regex” to treat alternate plus “RSS” in the title as a feed. Personally, I don’t really care enough about people who refuse to use an unregisterable “mime type” that is not what they serve in their autodiscovery link to do anything about it, but I did like having something to tell them other than “tough luck, suck it up.”

  2. The “in progress” events were not actually removed. What was changed is that they are now dispatched as simple events and therefore no longer expose information on the download process since that was already exposed in more detail through other means.

  3. “Standards are like sex; one mistake, and you’re stuck supporting it forever!”

    bad taste joke

    childrens are not mistakes

    anyway thank for the html5 update