- From: poot <cvsmail@w3.org>
- Date: Wed, 1 Dec 2010 09:48:25 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: ref rfc2397 where appropriate (whatwg r5693)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4560&r2=1.4561&f=h
http://html5.org/tools/web-apps-tracker?from=5692&to=5693
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4560
retrieving revision 1.4561
diff -u -d -r1.4560 -r1.4561
--- Overview.html 1 Dec 2010 00:26:37 -0000 1.4560
+++ Overview.html 1 Dec 2010 00:46:56 -0000 1.4561
@@ -2412,7 +2412,8 @@
specification that defines the resource's format. For CSS resources,
only <code title="">@import</code> rules introduce <a href="#critical-subresources">critical
subresources</a>; other resources, e.g. fonts or backgrounds, are
- not.<h4 id="xml"><span class="secno">2.1.2 </span>XML</h4><p id="html-namespace">To ease migration from HTML to XHTML, UAs
+ not.<p>The term <dfn id="data-protocol" title="data protocol"><code title="">data:</code>
+ URL</dfn> refers to <a href="#url" title="URL">URLs</a> that use the <code title="">data:</code> scheme. <a href="#refsRFC2397">[RFC2397]</a><h4 id="xml"><span class="secno">2.1.2 </span>XML</h4><p id="html-namespace">To ease migration from HTML to XHTML, UAs
conforming to this specification will place elements in HTML in the
<code>http://www.w3.org/1999/xhtml</code> namespace, at least for
the purposes of the DOM and CSS. The term "<dfn id="html-elements">HTML
@@ -25693,8 +25694,7 @@
<dd>
- <p>Returns a <code title="">data:</code> URL for the image in the
- canvas.</p>
+ <p>Returns a <a href="#data-protocol" title="data protocol"><code title="">data:</code> URL</a> for the image in the canvas.</p>
<p>The first argument, if provided, controls the type of the image
to be returned (e.g. PNG or JPEG). The default is <code title="">image/png</code>; that type is also used if the given
@@ -25707,17 +25707,20 @@
</dl><div class="impl">
<p>The <dfn id="dom-canvas-todataurl" title="dom-canvas-toDataURL"><code>toDataURL()</code></dfn> method
- must, when called with no arguments, return a <code title="">data:</code> URL containing a representation of the image
- as a PNG file. <a href="#refsPNG">[PNG]</a></p>
+ must, when called with no arguments, return a <a href="#data-protocol" title="data
+ protocol"><code title="">data:</code> URL</a> containing a
+ representation of the image as a PNG file. <a href="#refsPNG">[PNG]</a> <a href="#refsRFC2397">[RFC2397]</a></p>
<p>If the canvas has no pixels (i.e. either its horizontal dimension
or its vertical dimension is zero) then the method must return the
- string "<code title="">data:,</code>". (This is the shortest <code title="">data:</code> URL; it represents the empty string in a <code title="">text/plain</code> resource.)</p>
+ string "<code title="">data:,</code>". (This is the shortest <a href="#data-protocol" title="data protocol"><code title="">data:</code> URL</a>; it
+ represents the empty string in a <code title="">text/plain</code>
+ resource.)</p>
<p>When the <code title="dom-canvas-toDataURL"><a href="#dom-canvas-todataurl">toDataURL(<var title="">type</var>)</a></code> method is called with one <em>or
- more</em> arguments, it must return a <code title="">data:</code>
- URL containing a representation of the image in the format given by
- <var title="">type</var>. The possible values are <a href="#mime-type" title="MIME
+ more</em> arguments, it must return a <a href="#data-protocol" title="data
+ protocol"><code title="">data:</code> URL</a> containing a
+ representation of the image in the format given by <var title="">type</var>. The possible values are <a href="#mime-type" title="MIME
type">MIME types</a> with no parameters, for example
<code>image/png</code>, <code>image/jpeg</code>, or even maybe
<code>image/svg+xml</code> if the implementation actually keeps
@@ -25727,15 +25730,17 @@
<p>For image types that do not support an alpha channel, the image
must be composited onto a solid black background using the
source-over operator, and the resulting image must be the one used
- to create the <code title="">data:</code> URL.</p>
+ to create the <a href="#data-protocol" title="data protocol"><code title="">data:</code> URL</a>.</p>
<p>Only support for <code>image/png</code> is required. User agents
may support other types. If the user agent does not support the
requested type, it must return the image using the PNG format.</p>
- <p>User agents must <a href="#converted-to-ascii-lowercase" title="converted to ASCII lowercase">convert the
- provided type to ASCII lowercase</a> before establishing if they
- support that type and before creating the <code title="">data:</code> URL.</p>
+ <p>User agents must <a href="#converted-to-ascii-lowercase" title="converted to ASCII
+ lowercase">convert the provided type to ASCII lowercase</a>
+ before establishing if they support that type and before creating
+ the <a href="#data-protocol" title="data protocol"><code title="">data:</code>
+ URL</a>.</p>
</div><p class="note">When trying to use types other than
<code>image/png</code>, authors can check if the image was really
@@ -25771,6 +25776,10 @@
more carefully control compression settings, image metadata,
etc.</p>
+ <!-- should we explicitly require the URL to be base64-encoded and
+ not have any parameters, to ensure the same exact URL is generated
+ in each browser? -->
+
</div><div class="impl">
<h5 id="color-spaces-and-color-correction"><span class="secno">4.8.11.1 </span>Color spaces and color correction</h5>
@@ -37974,9 +37983,10 @@
resulting escaped string. <a href="#refsRFC3986">[RFC3986]</a></p>
<p><a href="#navigate">Navigate</a><!--DONAV form--> <var title="">target
- browsing context</var> to the potentially modified <var title="">action</var>. If <var title="">replace</var> is true,
- then <var title="">target browsing context</var> must be
- navigated with <a href="#replacement-enabled">replacement enabled</a>.</p>
+ browsing context</var> to the potentially modified <var title="">action</var> (which will be a <a href="#data-protocol" title="data
+ protocol"><code title="">data:</code> URL</a>). If <var title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <a href="#replacement-enabled">replacement
+ enabled</a>.</p>
</dd>
@@ -42533,17 +42543,20 @@
<dt>If a <code><a href="#document">Document</a></code> or image was generated from a
- <code title="">data:</code> URL that was returned as the location
- of an HTTP redirect (<a href="#concept-http-equivalent-codes" title="concept-http-equivalent-codes">or equivalent</a> in
- other protocols)</dt>
+ <a href="#data-protocol" title="data protocol"><code title="">data:</code>
+ URL</a> that was returned as the location of an HTTP redirect
+ (<a href="#concept-http-equivalent-codes" title="concept-http-equivalent-codes">or equivalent</a>
+ in other protocols)</dt>
<dd>The <a href="#origin">origin</a> is the <a href="#origin">origin</a> of the
- <a href="#url">URL</a> that redirected to the <code title="">data:</code> URL.</dd>
+ <a href="#url">URL</a> that redirected to the <a href="#data-protocol" title="data
+ protocol"><code title="">data:</code> URL</a>.</dd>
<dt>If a <code><a href="#document">Document</a></code> or image was generated from a
- <code title="">data:</code> URL found in another
- <code><a href="#document">Document</a></code> or in a script</dt>
+ <a href="#data-protocol" title="data protocol"><code title="">data:</code>
+ URL</a> found in another <code><a href="#document">Document</a></code> or in a
+ script</dt>
<dd>The <a href="#origin">origin</a> is the <a href="#origin">origin</a> of the
<code><a href="#document">Document</a></code> or script that initiated the <a href="#navigate" title="navigate">navigation</a> to that <a href="#url">URL</a>.</dd>
@@ -42566,8 +42579,8 @@
<dt>If a <code><a href="#document">Document</a></code> or image was obtained in some
- other manner (e.g. a <code title="">data:</code> URL typed in by
- the user, a <code><a href="#document">Document</a></code> created using the <code title="dom-DOMImplementation-createDocument"><a href="#dom-domimplementation-createdocument">createDocument()</a></code>
+ other manner (e.g. a <a href="#data-protocol" title="data protocol"><code title="">data:</code> URL</a> typed in by the user, a
+ <code><a href="#document">Document</a></code> created using the <code title="dom-DOMImplementation-createDocument"><a href="#dom-domimplementation-createdocument">createDocument()</a></code>
API, etc)</dt>
<dd>The <a href="#origin">origin</a> is a globally unique identifier
@@ -70560,6 +70573,10 @@
<dd><cite><a href="http://tools.ietf.org/html/rfc2388">Returning Values from
Forms: multipart/form-data</a></cite>, L. Masinter. IETF.</dd>
+ <dt id="refsRFC2397">[RFC2397]</dt>
+ <dd><cite><a href="http://tools.ietf.org/html/rfc2397">The "data"
+ URL scheme</a></cite>, L. Masinter. IETF.</dd>
+
<dt id="refsRFC2425">[RFC2425]</dt>
<dd><cite><a href="http://tools.ietf.org/html/rfc2425">A MIME
Content-Type for Directory Information</a></cite>, T. Howes,
@@ -71217,6 +71234,7 @@
Paul Norman,
Per-Erik Brodin,
Perry Smith,
+ Peter Beverloo,
Peter Karlsson,
Peter Kasting,
Peter Stark,
Received on Wednesday, 1 December 2010 00:48:55 UTC