[html5] r8532 - [e] (0) Some cleanup in the top parts of the spec Affected topics: DOM APIs, HTML
whatwg at whatwg.org
whatwg at whatwg.org
Thu Mar 6 14:55:24 PST 2014
Author: ianh
Date: 2014-03-06 14:55:23 -0800 (Thu, 06 Mar 2014)
New Revision: 8532
Modified:
complete.html
index
source
Log:
[e] (0) Some cleanup in the top parts of the spec
Affected topics: DOM APIs, HTML
Modified: complete.html
===================================================================
--- complete.html 2014-03-06 19:48:44 UTC (rev 8531)
+++ complete.html 2014-03-06 22:55:23 UTC (rev 8532)
@@ -3909,9 +3909,8 @@
<p>The term <dfn id=default-object-size>default object size</dfn> is also defined in the <cite>CSS Image Values and
Replaced Content</cite> specification. <a href=#refsCSSIMAGES>[CSSIMAGES]</a></p>
-<!--CLEANUP-->
- <p>Implementations that support scripting must support the CSS Object Model. The
- following features and terms are defined in the CSSOM specifications: <a href=#refsCSSOM>[CSSOM]</a> <a href=#refsCSSOMVIEW>[CSSOMVIEW]</a>
+ <p>Implementations that support scripting must support the CSS Object Model. The following
+ features and terms are defined in the CSSOM specifications: <a href=#refsCSSOM>[CSSOM]</a> <a href=#refsCSSOMVIEW>[CSSOMVIEW]</a>
<ul class=brief><li><dfn id=screen><code>Screen</code></dfn></li>
<li><dfn id=linkstyle><code>LinkStyle</code></dfn></li>
@@ -7848,9 +7847,10 @@
<code><a href=#htmloptionscollection>HTMLOptionsCollection</a></code> interface must act like the <code title=dom-HTMLCollection-namedItem>namedItem()</code> method on the ancestor
<code><a href=#htmlcollection>HTMLCollection</a></code> interface.</p>
-<!--CLEANUP-->
<p>When the user agent is to <dfn id=dom-htmloptionscollection-setter title=dom-HTMLOptionsCollection-setter>set the value of a new
- indexed property or set the value of an existing indexed property</dfn> for a given property index <var title="">index</var> to a new value <var title="">value</var>, it must run the following algorithm:</p>
+ indexed property or set the value of an existing indexed property</dfn> for a given property index
+ <var title="">index</var> to a new value <var title="">value</var>, it must run the following
+ algorithm:</p>
<ol><li><p>If <var title="">value</var> is null, invoke the steps for the <code title=dom-HTMLOptionsCollection-remove><a href=#dom-htmloptionscollection-remove>remove</a></code> method with <var title="">index</var> as
the argument, and abort these steps.</li>
@@ -8121,11 +8121,9 @@
<h4 id=transferable-objects><span class=secno>2.7.5 </span>Transferable objects</h4>
-<!--CLEANUP-->
- <p>Some objects support being copied and closed in one operation.
- This is called <i>transferring</i> the object, and is used in
- particular to transfer ownership of unsharable or expensive
- resources across worker boundaries.</p>
+ <p>Some objects support being copied and closed in one operation. This is called
+ <i>transferring</i> the object, and is used in particular to transfer ownership of unsharable or
+ expensive resources across worker boundaries.</p>
<p>The following <code><a href=#transferable>Transferable</a></code> types exist:</p>
@@ -8138,20 +8136,17 @@
<pre class=idl>typedef (<a href=#arraybuffer>ArrayBuffer</a> or <a href=#canvasproxy>CanvasProxy</a> or <a href=#messageport>MessagePort</a>) <dfn id=transferable>Transferable</dfn>;</pre>
-<!--CLEANUP-->
- <p>To <dfn id=transfer-a-transferable-object>transfer a <code>Transferable</code> object</dfn> to a
- new owner, the user agent must run the steps defined for the type of
- object in question. The steps will return a new object of the same
- type, and will permanently <dfn id=concept-transferable-neutered title=concept-Transferable-neutered>neuter</dfn> the original
- object. (This is an irreversible and non-idempotent operation; once
- an object has been transferred, it cannot be transferred, or indeed
- used, again.)</p>
+ <p>To <dfn id=transfer-a-transferable-object>transfer a <code>Transferable</code> object</dfn> to a new owner, the user agent must
+ run the steps defined for the type of object in question. The steps will return a new object of
+ the same type, and will permanently <dfn id=concept-transferable-neutered title=concept-Transferable-neutered>neuter</dfn> the
+ original object. (This is an irreversible and non-idempotent operation; once an object has been
+ transferred, it cannot be transferred, or indeed used, again.)</p>
<p id=transferArrayBuffer>To <a href=#transfer-a-transferable-object title="transfer a Transferable object">transfer</a> an
- <code><a href=#arraybuffer>ArrayBuffer</a></code> object <var title="">old</var> to a new owner <var title="">owner</var>,
- a user agent must create a new <code><a href=#arraybuffer>ArrayBuffer</a></code> object pointing at the same underlying
- data as <var title="">old</var>, thus obtaining <var title="">new</var>, must <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neuter</a> the <var title="">old</var> object, and must
- finally return <var title="">new</var>. <a href=#refsECMA262>[ECMA262]</a></p>
+ <code><a href=#arraybuffer>ArrayBuffer</a></code> object <var title="">old</var> to a new owner <var title="">owner</var>, a user agent must create a new <code><a href=#arraybuffer>ArrayBuffer</a></code> object pointing at
+ the same underlying data as <var title="">old</var>, thus obtaining <var title="">new</var>,
+ must <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neuter</a> the <var title="">old</var>
+ object, and must finally return <var title="">new</var>. <a href=#refsECMA262>[ECMA262]</a></p>
<!-- I'm expecting this section to move to the JS spec eventually so I'm leaving it as is for now -->
<p class=note>Rules for how to <a href=#transferCanvasProxy>transfer a
Modified: index
===================================================================
--- index 2014-03-06 19:48:44 UTC (rev 8531)
+++ index 2014-03-06 22:55:23 UTC (rev 8532)
@@ -3909,9 +3909,8 @@
<p>The term <dfn id=default-object-size>default object size</dfn> is also defined in the <cite>CSS Image Values and
Replaced Content</cite> specification. <a href=#refsCSSIMAGES>[CSSIMAGES]</a></p>
-<!--CLEANUP-->
- <p>Implementations that support scripting must support the CSS Object Model. The
- following features and terms are defined in the CSSOM specifications: <a href=#refsCSSOM>[CSSOM]</a> <a href=#refsCSSOMVIEW>[CSSOMVIEW]</a>
+ <p>Implementations that support scripting must support the CSS Object Model. The following
+ features and terms are defined in the CSSOM specifications: <a href=#refsCSSOM>[CSSOM]</a> <a href=#refsCSSOMVIEW>[CSSOMVIEW]</a>
<ul class=brief><li><dfn id=screen><code>Screen</code></dfn></li>
<li><dfn id=linkstyle><code>LinkStyle</code></dfn></li>
@@ -7848,9 +7847,10 @@
<code><a href=#htmloptionscollection>HTMLOptionsCollection</a></code> interface must act like the <code title=dom-HTMLCollection-namedItem>namedItem()</code> method on the ancestor
<code><a href=#htmlcollection>HTMLCollection</a></code> interface.</p>
-<!--CLEANUP-->
<p>When the user agent is to <dfn id=dom-htmloptionscollection-setter title=dom-HTMLOptionsCollection-setter>set the value of a new
- indexed property or set the value of an existing indexed property</dfn> for a given property index <var title="">index</var> to a new value <var title="">value</var>, it must run the following algorithm:</p>
+ indexed property or set the value of an existing indexed property</dfn> for a given property index
+ <var title="">index</var> to a new value <var title="">value</var>, it must run the following
+ algorithm:</p>
<ol><li><p>If <var title="">value</var> is null, invoke the steps for the <code title=dom-HTMLOptionsCollection-remove><a href=#dom-htmloptionscollection-remove>remove</a></code> method with <var title="">index</var> as
the argument, and abort these steps.</li>
@@ -8121,11 +8121,9 @@
<h4 id=transferable-objects><span class=secno>2.7.5 </span>Transferable objects</h4>
-<!--CLEANUP-->
- <p>Some objects support being copied and closed in one operation.
- This is called <i>transferring</i> the object, and is used in
- particular to transfer ownership of unsharable or expensive
- resources across worker boundaries.</p>
+ <p>Some objects support being copied and closed in one operation. This is called
+ <i>transferring</i> the object, and is used in particular to transfer ownership of unsharable or
+ expensive resources across worker boundaries.</p>
<p>The following <code><a href=#transferable>Transferable</a></code> types exist:</p>
@@ -8138,20 +8136,17 @@
<pre class=idl>typedef (<a href=#arraybuffer>ArrayBuffer</a> or <a href=#canvasproxy>CanvasProxy</a> or <a href=#messageport>MessagePort</a>) <dfn id=transferable>Transferable</dfn>;</pre>
-<!--CLEANUP-->
- <p>To <dfn id=transfer-a-transferable-object>transfer a <code>Transferable</code> object</dfn> to a
- new owner, the user agent must run the steps defined for the type of
- object in question. The steps will return a new object of the same
- type, and will permanently <dfn id=concept-transferable-neutered title=concept-Transferable-neutered>neuter</dfn> the original
- object. (This is an irreversible and non-idempotent operation; once
- an object has been transferred, it cannot be transferred, or indeed
- used, again.)</p>
+ <p>To <dfn id=transfer-a-transferable-object>transfer a <code>Transferable</code> object</dfn> to a new owner, the user agent must
+ run the steps defined for the type of object in question. The steps will return a new object of
+ the same type, and will permanently <dfn id=concept-transferable-neutered title=concept-Transferable-neutered>neuter</dfn> the
+ original object. (This is an irreversible and non-idempotent operation; once an object has been
+ transferred, it cannot be transferred, or indeed used, again.)</p>
<p id=transferArrayBuffer>To <a href=#transfer-a-transferable-object title="transfer a Transferable object">transfer</a> an
- <code><a href=#arraybuffer>ArrayBuffer</a></code> object <var title="">old</var> to a new owner <var title="">owner</var>,
- a user agent must create a new <code><a href=#arraybuffer>ArrayBuffer</a></code> object pointing at the same underlying
- data as <var title="">old</var>, thus obtaining <var title="">new</var>, must <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neuter</a> the <var title="">old</var> object, and must
- finally return <var title="">new</var>. <a href=#refsECMA262>[ECMA262]</a></p>
+ <code><a href=#arraybuffer>ArrayBuffer</a></code> object <var title="">old</var> to a new owner <var title="">owner</var>, a user agent must create a new <code><a href=#arraybuffer>ArrayBuffer</a></code> object pointing at
+ the same underlying data as <var title="">old</var>, thus obtaining <var title="">new</var>,
+ must <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neuter</a> the <var title="">old</var>
+ object, and must finally return <var title="">new</var>. <a href=#refsECMA262>[ECMA262]</a></p>
<!-- I'm expecting this section to move to the JS spec eventually so I'm leaving it as is for now -->
<p class=note>Rules for how to <a href=#transferCanvasProxy>transfer a
Modified: source
===================================================================
--- source 2014-03-06 19:48:44 UTC (rev 8531)
+++ source 2014-03-06 22:55:23 UTC (rev 8532)
@@ -2659,10 +2659,9 @@
<p>The term <dfn>default object size</dfn> is also defined in the <cite>CSS Image Values and
Replaced Content</cite> specification. <a href="#refsCSSIMAGES">[CSSIMAGES]</a></p>
-<!--CLEANUP-->
- <p>Implementations that support scripting must support the CSS Object Model. The
- following features and terms are defined in the CSSOM specifications: <a
- href="#refsCSSOM">[CSSOM]</a> <a href="#refsCSSOMVIEW">[CSSOMVIEW]</a>
+ <p>Implementations that support scripting must support the CSS Object Model. The following
+ features and terms are defined in the CSSOM specifications: <a href="#refsCSSOM">[CSSOM]</a> <a
+ href="#refsCSSOMVIEW">[CSSOMVIEW]</a>
<ul class="brief">
<li><dfn><code>Screen</code></dfn></li>
@@ -7358,10 +7357,10 @@
data-x="dom-HTMLCollection-namedItem">namedItem()</code> method on the ancestor
<code>HTMLCollection</code> interface.</p>
-<!--CLEANUP-->
<p>When the user agent is to <dfn data-x="dom-HTMLOptionsCollection-setter">set the value of a new
- indexed property or set the value of an existing indexed property</dfn> for a given property index <var data-x="">index</var> to a new value <var
- data-x="">value</var>, it must run the following algorithm:</p>
+ indexed property or set the value of an existing indexed property</dfn> for a given property index
+ <var data-x="">index</var> to a new value <var data-x="">value</var>, it must run the following
+ algorithm:</p>
<ol>
@@ -7670,11 +7669,9 @@
<h4>Transferable objects</h4>
-<!--CLEANUP-->
- <p>Some objects support being copied and closed in one operation.
- This is called <i>transferring</i> the object, and is used in
- particular to transfer ownership of unsharable or expensive
- resources across worker boundaries.</p>
+ <p>Some objects support being copied and closed in one operation. This is called
+ <i>transferring</i> the object, and is used in particular to transfer ownership of unsharable or
+ expensive resources across worker boundaries.</p>
<p>The following <code>Transferable</code> types exist:</p>
@@ -7690,22 +7687,18 @@
<pre class="idl">typedef (<span>ArrayBuffer</span> or <span>CanvasProxy</span> or <span>MessagePort</span>) <dfn>Transferable</dfn>;</pre>
-<!--CLEANUP-->
- <p>To <dfn>transfer a <code>Transferable</code> object</dfn> to a
- new owner, the user agent must run the steps defined for the type of
- object in question. The steps will return a new object of the same
- type, and will permanently <dfn
- data-x="concept-Transferable-neutered">neuter</dfn> the original
- object. (This is an irreversible and non-idempotent operation; once
- an object has been transferred, it cannot be transferred, or indeed
- used, again.)</p>
+ <p>To <dfn>transfer a <code>Transferable</code> object</dfn> to a new owner, the user agent must
+ run the steps defined for the type of object in question. The steps will return a new object of
+ the same type, and will permanently <dfn data-x="concept-Transferable-neutered">neuter</dfn> the
+ original object. (This is an irreversible and non-idempotent operation; once an object has been
+ transferred, it cannot be transferred, or indeed used, again.)</p>
<p id="transferArrayBuffer">To <span data-x="transfer a Transferable object">transfer</span> an
- <code>ArrayBuffer</code> object <var data-x="">old</var> to a new owner <var data-x="">owner</var>,
- a user agent must create a new <code>ArrayBuffer</code> object pointing at the same underlying
- data as <var data-x="">old</var>, thus obtaining <var data-x="">new</var>, must <span
- data-x="concept-Transferable-neutered">neuter</span> the <var data-x="">old</var> object, and must
- finally return <var data-x="">new</var>. <a href="#refsECMA262">[ECMA262]</a></p>
+ <code>ArrayBuffer</code> object <var data-x="">old</var> to a new owner <var
+ data-x="">owner</var>, a user agent must create a new <code>ArrayBuffer</code> object pointing at
+ the same underlying data as <var data-x="">old</var>, thus obtaining <var data-x="">new</var>,
+ must <span data-x="concept-Transferable-neutered">neuter</span> the <var data-x="">old</var>
+ object, and must finally return <var data-x="">new</var>. <a href="#refsECMA262">[ECMA262]</a></p>
<!-- I'm expecting this section to move to the JS spec eventually so I'm leaving it as is for now -->
<p class="note">Rules for how to <a href="#transferCanvasProxy">transfer a
More information about the Commit-Watchers
mailing list