Categories
HTML5 Specs

Apple, Opera, and Mozilla: Why are you working against open standards?

I have a question for Mozilla, Opera, and Apple: why are you working against open standards? Why do you still support an organization, known as the WhatWG, that has proven itself to be detrimental to an open and inclusive specification development effort? Recently I wrote about a kerfuffle that happened within the HTML WG, when the editor, Ian […]

Categories
Specs

The W3C bites back?

Recovered from the Wayback Machine. This has been a long time coming, and not sure where it will go. It started innocuously enough: remove a paragraph associated with the alt attribute, about user agents using some form of heuristics to determine replacement text. It wasn’t associated with a bug—it predated the current decision process. It […]

Categories
HTML5 Technology

Too much crap

I tried to find a web page to link in my last story, about the recent discussion surrounding Apple’s new HTML5 demo that deliberately prevents other browsers from accessing the examples. I finally had to link my own Twitter note about the problem, because every site that wrote about the issue had too much crap […]

Categories
HTML5

HTML 5 update

I’d provide another update on my HTML5 change proposals, but no co-chair decision has yet been published. There was a note in the last HTML WG teleconference minutes that decisions on three of the items, including two of mine, were ready to be published last Thursday, but nothing has appeared in the HTML WG email list. As […]

Categories
HTML5 Specs

Progress Element: what I’ve found

To recap my weekend effort with the WebKit nightly implementation of the HTML5 progress element: I created a application that uses the progress element and provides a text-based fallback for the element. You need to use setAttribute and getAttribute to get the progress element’s value attribute, as accessing the attribute directly on the object only works when […]