In an e-mail sent to the firstname.lastname@example.org mailing list on Wednesday, Microsoft’s Eliot Graf proposedremoving the Canvas element, which is used to create complex vector animations in the browser without plug-ins, from the HTML5 specification. Graf also proposed launching a new, separate specification for the Canvas 2D API.
In his mail describing why he created a separate Canvas 2D API specification, Doug Schepers wrote :
> There is a chance that currently Canvas could be a blocker on progress
> for the HTML5 spec, and at this point, Canvas is so widely implemented
> that I don’t think it’s at risk, so I hope this isn’t disruptive. I am
> available to help with any editing that needs doing, but I hope that
> others will also work with this draft, and step into the editor role.
At Microsoft, we agree with the sentiments expressed by Doug, Maciej , and others about creating a separate Canvas 2D API specification.  We are prepared to offer editorial resources to aid in the completion of this separate specification. We have looked over Doug’s initial document, made some editorial enhancements, and are prepared to follow through in taking feedback and maintaining the specification.
We believe that some sort of accessibility API functionality is needed in the canvas element. However, the exact nature and depth of that functionality presents a dilemma that may block progress on the HTML5 spec. We also think that the Canvas 2D API may be a desirable feature used in other technologies such as SVG.
Starting with Doug Schepers’ initial draft, we made changes to get the document to adhere to the W3C PubRules , enhance readability, and improve logical flow of the document. In addition, we foresee adding sample code throughout the specification, where appropriate. No normative changes have been made. As with all drafts, the Canvas 2D API specification is still a work in progress. We would like to solicit feedback about the changes that were made (see below TODO) and about further changes that the working group would like to see.
Our updated version is published at http://dev.w3.org/html5/canvas-api/canvas-2d-api.html.
Microsoft Internet Explorer is the only modern browser with no plans to support Canvas — Firefox, Chrome, Safari and Opera all do. Redmond’s opposition makes sense, as the animation capabilities Canvas provides would conflict with Microsoft’s plans to speed adoption of its Silverlight platform, which affords web authors many of the same capabilities using a proprietary plug-in and commercial development software.
Several list members pointed out that if Microsoft has the resources to author the spec independent of HTML5, those resources could be better spent building support for Canvas into the browser.
A follow-up response from Ian Hickson, a Google employee who is the primary editor of the HTML5 spec, points out a few clear problems with this strategy and stresses that it doesn’t seem list a good idea:
IF we’re going to split out the 2D API — and I’m not really sure if at this point that’s something we should do, frankly — then I would much rather we do it based on the text in the HTML5 spec now, and would much rather we have an editor who is able to give this the full-time attention that it needs.
However, I’m really not sure at this point that it even makes sense to extract the API anymore. The API intergrates pretty tightly with the rest of HTML, for example it refers to HTMLVideoElements, the HTML5 “structured clone” feature is defined in terms of canvas interfaces, and so on. There would have to be a two-way reference, which would be a maintenance nightmare, and which would just delay the progress of both documents.
What are the problems that we are trying to solve by splitting out the API at this point?