周三,一封電子郵件發送到public-html@w3.org，微軟的Eliot Graf建議刪除Canvas元素，它是用于創建無插件的瀏覽器的復雜的矢量動畫插件的html5規范。Eliot Graf建議發起一個新的單獨的Canvas API規范.
以下是該電子郵件部分內容:
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 http://dev.w3.org/html5/canvas-api/canvas-2d-api.html.
[1] http://lists.w3.org/Archives/Public/public-canvas-api/2009JulSep/0002.html
[2] http://lists.w3.org/Archives/Public/public-canvas-api/2009JulSep/0007.html
[3] http://lists.w3.org/Archives/Public/public-html/2009Aug/0628.html
[3] http://www.w3.org/2005/07/pubrules[…]
IE瀏覽器(Microsoft Internet Explorer)是唯一一個不支持Canvas的瀏覽器，而Firefox,Safari和Opear現在都已經支持了。微軟的反對是沒有道理的，因為Canvas提成動畫功能將對微軟的計劃Silverlight平臺有影響，它是利用Silverlight編寫商業軟件的作者相沖突.
幾位成員指出，如果微軟的開發者能夠從HMTL5的規范中獨立，這些資源可以更好地用被瀏覽器支持。
谷歌一員工是html5規范的編輯者，他回應這一說法，他說這一戰略有幾個明顯的問題點，并說這不是一個好的主意：
如果我們要分裂出2D API的-我的確不知道，如果在這一點上，這是我們應該做的，坦率地說-那么我寧愿我們這樣做的基礎上，在html5規范文字了，寧愿有一個編輯誰是能夠給這個全職注意，它的需求。
不過，我真的不知道在這一點上，它甚至有意義的提取API的了。API和HTML緊密的聯系著，例如它是指HTML Video元素的html5“結構克隆”功能的定義是帆布接口方面，等等。有將是一個雙向的參考，這將是一個維修噩夢，這將只是推遲了兩個文件的進展。
有什么困難，我們正在試圖通過了API的分裂解決這個問題呢？