周三,一封電子郵件發(fā)送到public-html@w3.org，微軟的Eliot Graf建議刪除Canvas元素，它是用于創(chuàng)建無(wú)插件的瀏覽器的復(fù)雜的矢量動(dòng)畫(huà)插件的html5規(guī)范。Eliot Graf建議發(fā)起一個(gè)新的單獨(dú)的Canvas API規(guī)范.
以下是該電子郵件部分內(nèi)容:
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)是唯一一個(gè)不支持Canvas的瀏覽器，而Firefox,Safari和Opear現(xiàn)在都已經(jīng)支持了。微軟的反對(duì)是沒(méi)有道理的，因?yàn)镃anvas提成動(dòng)畫(huà)功能將對(duì)微軟的計(jì)劃Silverlight平臺(tái)有影響，它是利用Silverlight編寫(xiě)商業(yè)軟件的作者相沖突.
幾位成員指出，如果微軟的開(kāi)發(fā)者能夠從HMTL5的規(guī)范中獨(dú)立，這些資源可以更好地用被瀏覽器支持。
谷歌一員工是html5規(guī)范的編輯者，他回應(yīng)這一說(shuō)法，他說(shuō)這一戰(zhàn)略有幾個(gè)明顯的問(wèn)題點(diǎn)，并說(shuō)這不是一個(gè)好的主意：
如果我們要分裂出2D API的-我的確不知道，如果在這一點(diǎn)上，這是我們應(yīng)該做的，坦率地說(shuō)-那么我寧愿我們這樣做的基礎(chǔ)上，在html5規(guī)范文字了，寧愿有一個(gè)編輯誰(shuí)是能夠給這個(gè)全職注意，它的需求。
不過(guò)，我真的不知道在這一點(diǎn)上，它甚至有意義的提取API的了。API和HTML緊密的聯(lián)系著，例如它是指HTML Video元素的html5“結(jié)構(gòu)克隆”功能的定義是帆布接口方面，等等。有將是一個(gè)雙向的參考，這將是一個(gè)維修噩夢(mèng)，這將只是推遲了兩個(gè)文件的進(jìn)展。
有什么困難，我們正在試圖通過(guò)了API的分裂解決這個(gè)問(wèn)題呢？