Canvas 2D API specification update

In his mail describing why he created a separate Canvas 2D API specification, Doug Schepers wrote [1]: 

> 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 [2], and others about creating a separate Canvas 2D API specification. [3]  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 [4], 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 


PubRules verified or applied throughout the specification, including fixing broken links and applying accessibility requirements.
Addition of normative references to remove reliance upon links to HTML5 specification
General language, formatting, and logical edits, such as:
	Alphabetizing attributes and methods within existing sections
	Editing sentences to make them easier to understand
	Breaking long sentences, noun stacks, etc. to enhance readability
	Reordering paragraphs to create more seamless flow within sections

Received on Wednesday, 21 October 2009 21:02:01 UTC