[html5] r5693 - [e] (0) ref rfc2397 where appropriate
whatwg at whatwg.org
whatwg at whatwg.org
Tue Nov 30 16:46:40 PST 2010
Author: ianh
Date: 2010-11-30 16:46:39 -0800 (Tue, 30 Nov 2010)
New Revision: 5693
Modified:
complete.html
index
source
Log:
[e] (0) ref rfc2397 where appropriate
Modified: complete.html
===================================================================
--- complete.html 2010-12-01 00:26:28 UTC (rev 5692)
+++ complete.html 2010-12-01 00:46:39 UTC (rev 5693)
@@ -2681,7 +2681,10 @@
subresources</a>; other resources, e.g. fonts or backgrounds, are
not.</p>
+ <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></p>
+
<h4 id=xml><span class=secno>2.1.2 </span>XML</h4>
<p id=html-namespace>To ease migration from HTML to XHTML, UAs
@@ -30918,8 +30921,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
@@ -30932,17 +30934,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
@@ -30952,15 +30957,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>
@@ -31002,6 +31009,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>
<!--2DCONTEXT-->
@@ -47681,9 +47692,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>
@@ -58052,17 +58064,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>
@@ -58085,8 +58100,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
@@ -71082,9 +71097,10 @@
<code><a href=#security_err>SECURITY_ERR</a></code> exception.</p>
<p class=note>Thus, scripts must be external files with the same
- scheme as the original page: you can't load a script from a <code title="">data:</code> URL or <code title="">javascript:</code>
- URL, and a <code>https:</code> page couldn't start workers using
- scripts with <code>http:</code> URLs.</p>
+ scheme as the original page: you can't load a script from a <a href=#data-protocol title="data protocol"><code title="">data:</code> URL</a> or
+ <a href=#javascript-protocol title="javascript protocol"><code title="">javascript:</code> URL</a>, and an <code>https:</code>
+ page couldn't start workers using scripts with <code>http:</code>
+ URLs.</p>
</li>
@@ -71205,9 +71221,10 @@
exception.</p>
<p class=note>Thus, scripts must be external files with the same
- scheme as the original page: you can't load a script from a <code title="">data:</code> URL or <code title="">javascript:</code>
- URL, and a <code>https:</code> page couldn't start workers using
- scripts with <code>http:</code> URLs.</p>
+ scheme as the original page: you can't load a script from a <a href=#data-protocol title="data protocol"><code title="">data:</code> URL</a> or
+ <a href=#javascript-protocol title="javascript protocol"><code title="">javascript:</code> URL</a>, and a <code>https:</code>
+ page couldn't start workers using scripts with <code>http:</code>
+ URLs.</p>
</li>
@@ -92445,6 +92462,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,
@@ -93108,6 +93129,7 @@
Paul Norman,
Per-Erik Brodin,
Perry Smith,
+ Peter Beverloo,
Peter Karlsson,
Peter Kasting,
Peter Stark,
Modified: index
===================================================================
--- index 2010-12-01 00:26:28 UTC (rev 5692)
+++ index 2010-12-01 00:46:39 UTC (rev 5693)
@@ -2658,7 +2658,10 @@
subresources</a>; other resources, e.g. fonts or backgrounds, are
not.</p>
+ <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></p>
+
<h4 id=xml><span class=secno>2.1.2 </span>XML</h4>
<p id=html-namespace>To ease migration from HTML to XHTML, UAs
@@ -30898,8 +30901,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
@@ -30912,17 +30914,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
@@ -30932,15 +30937,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>
@@ -30982,6 +30989,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>
<!--2DCONTEXT-->
@@ -47661,9 +47672,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>
@@ -58032,17 +58044,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>
@@ -58065,8 +58080,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
@@ -88504,6 +88519,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,
@@ -89186,6 +89205,7 @@
Paul Norman,
Per-Erik Brodin,
Perry Smith,
+ Peter Beverloo,
Peter Karlsson,
Peter Kasting,
Peter Stark,
Modified: source
===================================================================
--- source 2010-12-01 00:26:28 UTC (rev 5692)
+++ source 2010-12-01 00:46:39 UTC (rev 5693)
@@ -1574,7 +1574,11 @@
subresources</span>; other resources, e.g. fonts or backgrounds, are
not.</p>
+ <p>The term <dfn title="data protocol"><code title="">data:</code>
+ URL</dfn> refers to <span title="URL">URLs</span> that use the <code
+ title="">data:</code> scheme. <a href="#refsRFC2397">[RFC2397]</a></p>
+
<h4>XML</h4>
<p id="html-namespace">To ease migration from HTML to XHTML, UAs
@@ -33914,8 +33918,8 @@
<dd>
- <p>Returns a <code title="">data:</code> URL for the image in the
- canvas.</p>
+ <p>Returns a <span title="data protocol"><code
+ title="">data:</code> URL</span> 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
@@ -33932,21 +33936,24 @@
<p>The <dfn
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 <span title="data
+ protocol"><code title="">data:</code> URL</span> 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 <span
+ title="data protocol"><code title="">data:</code> URL</span>; it
+ represents the empty string in a <code title="">text/plain</code>
+ resource.)</p>
<p>When the <code title="dom-canvas-toDataURL">toDataURL(<var
title="">type</var>)</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 <span title="MIME
+ more</em> arguments, it must return a <span title="data
+ protocol"><code title="">data:</code> URL</span> containing a
+ representation of the image in the format given by <var
+ title="">type</var>. The possible values are <span title="MIME
type">MIME types</span> 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
@@ -33956,16 +33963,18 @@
<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 <span title="data protocol"><code
+ title="">data:</code> URL</span>.</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 <span title="converted to ASCII lowercase">convert the
- provided type to ASCII lowercase</span> before establishing if they
- support that type and before creating the <code
- title="">data:</code> URL.</p>
+ <p>User agents must <span title="converted to ASCII
+ lowercase">convert the provided type to ASCII lowercase</span>
+ before establishing if they support that type and before creating
+ the <span title="data protocol"><code title="">data:</code>
+ URL</span>.</p>
</div>
@@ -34017,6 +34026,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>
<!--END w3c-html--><!--2DCONTEXT-->
@@ -53600,9 +53613,11 @@
<p><span>Navigate</span><!--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 <span>replacement enabled</span>.</p>
+ title="">action</var> (which will be a <span title="data
+ protocol"><code title="">data:</code> URL</span>). If <var
+ title="">replace</var> is true, then <var title="">target
+ browsing context</var> must be navigated with <span>replacement
+ enabled</span>.</p>
</dd>
@@ -65950,19 +65965,20 @@
<dt>If a <code>Document</code> or image was generated from a
- <code title="">data:</code> URL that was returned as the location
- of an HTTP redirect (<span
- title="concept-http-equivalent-codes">or equivalent</span> in
- other protocols)</dt>
+ <span title="data protocol"><code title="">data:</code>
+ URL</span> that was returned as the location of an HTTP redirect
+ (<span title="concept-http-equivalent-codes">or equivalent</span>
+ in other protocols)</dt>
<dd>The <span>origin</span> is the <span>origin</span> of the
- <span>URL</span> that redirected to the <code
- title="">data:</code> URL.</dd>
+ <span>URL</span> that redirected to the <span title="data
+ protocol"><code title="">data:</code> URL</span>.</dd>
<dt>If a <code>Document</code> or image was generated from a
- <code title="">data:</code> URL found in another
- <code>Document</code> or in a script</dt>
+ <span title="data protocol"><code title="">data:</code>
+ URL</span> found in another <code>Document</code> or in a
+ script</dt>
<dd>The <span>origin</span> is the <span>origin</span> of the
<code>Document</code> or script that initiated the <span
@@ -65988,8 +66004,9 @@
<dt>If a <code>Document</code> or image was obtained in some
- other manner (e.g. a <code title="">data:</code> URL typed in by
- the user, a <code>Document</code> created using the <code
+ other manner (e.g. a <span title="data protocol"><code
+ title="">data:</code> URL</span> typed in by the user, a
+ <code>Document</code> created using the <code
title="dom-DOMImplementation-createDocument">createDocument()</code>
API, etc)</dt>
@@ -80385,10 +80402,12 @@
<code>SECURITY_ERR</code> exception.</p>
<p class="note">Thus, scripts must be external files with the same
- scheme as the original page: you can't load a script from a <code
- title="">data:</code> URL or <code title="">javascript:</code>
- URL, and a <code>https:</code> page couldn't start workers using
- scripts with <code>http:</code> URLs.</p>
+ scheme as the original page: you can't load a script from a <span
+ title="data protocol"><code title="">data:</code> URL</span> or
+ <span title="javascript protocol"><code
+ title="">javascript:</code> URL</span>, and an <code>https:</code>
+ page couldn't start workers using scripts with <code>http:</code>
+ URLs.</p>
</li>
@@ -80523,10 +80542,12 @@
exception.</p>
<p class="note">Thus, scripts must be external files with the same
- scheme as the original page: you can't load a script from a <code
- title="">data:</code> URL or <code title="">javascript:</code>
- URL, and a <code>https:</code> page couldn't start workers using
- scripts with <code>http:</code> URLs.</p>
+ scheme as the original page: you can't load a script from a <span
+ title="data protocol"><code title="">data:</code> URL</span> or
+ <span title="javascript protocol"><code
+ title="">javascript:</code> URL</span>, and a <code>https:</code>
+ page couldn't start workers using scripts with <code>http:</code>
+ URLs.</p>
</li>
@@ -106510,6 +106531,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,
@@ -107276,6 +107301,7 @@
Paul Norman,
Per-Erik Brodin,
Perry Smith,
+ Peter Beverloo,
Peter Karlsson,
Peter Kasting,
Peter Stark,
More information about the Commit-Watchers
mailing list