Archive for August, 2011
This week the HTML specification gained four new methods and also lost some weight due to higher quality “competing” proposals for editing related APIs.
registerContentHandler() gained four complementary methods.
isContentHandlerRegistered() to determine whether the user is already using the site in question to handle the specified scheme or media type, and
unregisterContentHandler() to give the site the ability to offer an opt-out user interface.
UndoManager proposal contained in the HTML specification has now been removed in favor of the work Ryosuke Niwa has been doing on UndoManager and DOM Transaction.
execCommand() method and friends have also been removed from the HTML specification in favor of the work Aryeh Gregor has been doing on HTML Editing APIs.
A couple of people from Google and Mozilla came together in Canada to discuss the various challenges authors face with editing on the web and how they can be tackled. Ehsan Akhgari wrote a detailed report Future of editing on the web that is well worth reading.
WHATWG Weekly is somewhat irregularly updated as its writer has a somewhat chaotic vacation schedule. The specification meanwhile keeps getting refined, with the latest significant change being a security update to
registerContentHandler(). These methods provide better platform integration, by letting web pages become responsible for handling e.g.
irc URLs. This security update introduces a whitelist for
registerProtocolHandler() along with the ability for everyone to mint their own whitelisted URL schemes that are required to start with
registerContentHandler() meanwhile gets a blacklist for the time being as a suitable way to define a whitelist has not been found.
UndoManager and DOM Transaction
Ryosuke Niwa has been working on an API proposal to manage the undo transaction history. This proposal is deemed better than what is currently in the HTML specification and is being sorted out on the WHATWG list. Once this is completed web applications will finally get proper undo/redo behavior.
HTML/XML Task Force
A while ago the W3C TAG set up a Task Force to investigate how HTML and XML can be more closely aligned. A preliminary report is available: HTML/XML Task Force Report.
W3C Community Groups
The W3C set up Community Groups the other day making it easier for people to develop standards at the W3C without all the overhead that previously entailed. Aryeh Gregor already set up the HTML Editing APIs Community Group to work on HTML Editing APIs. Feel free to join the group or start your own!
Component Model Update
Dimitri “good morning” Glazkov posted an update on working out the component model for the web (formerly XBL). To learn more check out the component model page on the WHATWG wiki which contains a good overview of the technology.
WHATWG Weekly has been on a little summer break. Since we were gone over hundred changes were made to the HTML specification, the W3C HTML5 Last Call period is over, and Maciej solicited input on HTML.next.
The changes made to the HTML specifications have been in response to Last Call comments, making clarifications, fixing typos, and a couple of relatively major changes, such as having interfaces inherit (e.g.
Window) from the
EventTarget interface rather than implement it. Take a look at the HTML5 Tracker for more detail.