- From: Charles Pritchard <chuck@jumis.com>
- Date: Tue, 06 Sep 2011 14:06:25 -0700
- To: public-canvas-api@w3.org
- Message-ID: <4E668B51.3090405@jumis.com>
I'd like to see the canvas 2d spec hosted on the hg repositories that some other specs are now on. http://dvcs.w3.org/hg <http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html> Hg is easier to manage than cvs. Given the current fork in WHATWG and W3C specs, it's a good time to move onto it. I further suggest following the domcore spec's templating style, in 2dcontext: http://dvcs.w3.org/hg/domcore/file/32037d398a47 http://dvcs.w3.org/hg/domcore/raw-file/32037d398a47/Overview.src.html Note the compiled version for w3c consumption: http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html And the compiled version for whatwg consumption: http://dvcs.w3.org/hg/domcore/raw-file/tip/dom-core.html As an aside- note that the HTML Canvas element specification from the WHATWG continues to ban interactive elements such as <select> from being present in the canvas subtree. This exception is not presented in the W3C specifications, thankfully. That specification will likely change, once additional vendors complete their support of the Canvas subtree. This working group has not encountered any vendors requesting that elements in the subtree be limited, apart from a short examination as to whether or not the <iframe> tag should be allowed within the subtree. It was agreed that it can be allowed, that the subtree poses no additional considerations as to DOM appendChild as an HTMLElement -Charles.
Received on Tuesday, 6 September 2011 21:07:03 UTC