- From: Eliot Graff <eliotgra@microsoft.com>
- Date: Wed, 28 Oct 2009 23:53:05 +0000
- To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>
Hello. The Canvas 2D API specification contains a number of TODOs, chief among them is seeing whether the spec can exist without links to normative materials in the HTML5 specification. I have searched the existing document and have found that 39 URLs reference the HTML5 specification in three main areas: -- Definitions of error messages -- Definitions from the Common Infrastructures (Section 2) of HTML5 -- References to HTML elements used as arguments (e.g. video, img, etc.) The particular instances are: LINK TEXT /**/# instances/**/ URL: http://dev.w3.org/html5/spec/.... OR http://www.w3.org/TR/html5/.... -------------------------------------------------------------------------------------------------- case-sensitive /**/ 2 /**/ spec/infrastructure.html#case-sensitive convert....to ASCII lowercase /**/ 1 /**/ spec/infrastructure.html#converted-to-ascii-lowercase in a /**/ 2 /**/ spec/infrastructure.html#in-a-document MIME types /**/ 1 /**/ spec/infrastructure.html#mime-type reflect /**/ 1 /**/ spec/infrastructure.html#reflect ....parsing non-negative integers /**/ 1 /**/ spec/infrastructure.html#rules-for-parsing-non-negative-integers space characters /**/ 2 /**/ spec/infrastructure.html#space-character valid non-negative integers /**/ 1 /**/ spec/infrastructure.html#valid-non-negative-integer INDEX_SIZE_ERR /**/ 11 /**/ spec/infrastructure.html#index_size_err INVALID_STATE_ERR /**/ 8 /**/ spec/infrastructure.html#invalid_state_err NOT_SUPPORTED_ERR /**/ 8 /**/ spec/infrastructure.html#not_supported_err SECURITY_ERR /**/ 2 /**/ spec/infrastructure.html#security_err SYNTAX_ERR /**/ 5 /**/ spec/infrastructure.html#syntax_err TYPE_MISMATCH_ERR /**/ 6 /**/ spec/infrastructure.html#type_mismatch_err h1 /**/ 1 /**/ spec/semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements canvas /**/ 1 /**/ spec/spec.html canvas /**/ 2 /**/ spec/the-canvas-element.html#the-canvas-element current playback position /**/ 2 /**/ spec/video.html#current-playback-position HAVE_METADATA /**/ 2 /**/ spec/video.html#dom-media-have_metadata HAVE_NOTHING /**/ 2 /**/ spec/video.html#dom-media-have_nothing readyState /**/ 2 /**/ spec/video.html#dom-media-readystate HTMLVideoElement /**/ 14 /**/ spec//video.html#htmlvideoelement video /**/ 2 /**/ spec/video.html#video complete /**/ 2 /**/ html5/text-level-semantics.html#dom-img-complete HTMLImageElement /**/ 14 /**/ html5/text-level-semantics.html#htmlimageelement img /**/ 3 /**/ html5/text-level-semantics.html#the-img-element height /**/ 1 /**/ html5/the-canvas-element.html#attr-dim-height width /**/ 1 /**/ html5/the-canvas-element.html#attr-dim-width HTMLCanvasElement /**/ 13 /**/ html5/the-canvas-element.html#htmlcanvaselement scripting is disabled /**/ 1 /**/ spec/browsers.html#concept-n-noscript scripting is enabled /**/ 1 /**/ spec/browsers.html#concept-n-script origin /**/ 4 /**/ spec/browsers.html#origin-0 same /**/ 4 /**/ spec/browsers.html#same-origin embedded content /**/ 1 /**/ spec/dom.html#embedded-content-2 fallback content /**/ 3 /**/ spec/dom.html#fallback-content directionality /**/ 5 /**/ spec/dom.html#the-directionality represents /**/ 1 /**/ spec/the-xhtml-syntax.html#represents As you can see, there are a few edge cases, but those are the overall patterns. I will be working through the draft to make it self-reliant where possible and identify any areas where this seems problematic. Feedback is welcome. Thanks, Eliot
Received on Wednesday, 28 October 2009 23:53:47 UTC