[giow] (0) Clarify that you can transfer a port more than once by avo…

…iding confusing terminology that suggested otherwise.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13717

git-svn-id: http://svn.whatwg.org/webapps@6653 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -8920,9 +8920,10 @@ <h4 id=transferable-objects><span class=secno>2.8.5 </span>Transferable objects<
   <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 neuter 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>
+  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>
 
   </div>
 
@@ -81589,9 +81590,9 @@ <h4 id=posting-messages><span class=secno>11.4.3 </span>Posting messages</h4>
 
       <p>If any object is listed in <var title="">transfer</var> more
       than once, or any of the <code><a href=#transferable>Transferable</a></code> objects
-      listed in <var title="">transfer</var> have already been <a href=#transfer-a-transferable-object title="transfer a Transferable object">transfered</a> once
-      before, then throw a <code><a href=#datacloneerror>DataCloneError</a></code> exception and
-      abort these steps.</p>
+      listed in <var title="">transfer</var> are marked as <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neutered</a>, then
+      throw a <code><a href=#datacloneerror>DataCloneError</a></code> exception and abort these
+      steps.</p>
 
      </li>
 
@@ -81603,9 +81604,9 @@ <h4 id=posting-messages><span class=secno>11.4.3 </span>Posting messages</h4>
       object">transferring</a> the object to the
       <code><a href=#window>Window</a></code> object on which the method was invoked, and
       add a mapping from the old object to the new transferred object
-      to <var title="">transfer map</var>. If the objects are
-      <code><a href=#messageport>MessagePort</a></code> objects, also append the new
-      transferred object to the <var title="">new ports</var>
+      to <var title="">transfer map</var>. For each new
+      <code><a href=#messageport>MessagePort</a></code> object obtained in this manner, append
+      the new transferred object to the <var title="">new ports</var>
       array.</p>
 
      </li>
@@ -82013,7 +82014,8 @@ <h4 id=message-ports><span class=secno>11.5.3 </span>Message ports</h4>
 
   </ol><p id=transferMessagePort>To <a href=#transfer-a-transferable-object title="transfer a Transferable
   object">transfer</a> a <code><a href=#messageport>MessagePort</a></code> object <var title="">old</var> to a new owner <var title="">owner</var>, a user
-  agent must <a href=#clone-a-port title="clone a port">clone</a> the <var title="">old</var> object with the cloned being owned by <var title="">owner</var>, and must return the resulting object.</p>
+  agent must <a href=#clone-a-port title="clone a port">clone</a> the <var title="">old</var> object with the clone being owned by <var title="">owner</var>, thus obtaining <var title="">new</var>, must
+  <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neuter</a> the <var title="">old</var> port, and must finally return <var title="">new</var>.</p>
 
   <hr><!-- v2-onclose
   <p>The <dfn title="dom-MessagePort-active"><code>active</code></dfn>

index

@@ -8920,9 +8920,10 @@ interface <dfn id=transferable>Transferable</dfn> { };</pre>
   <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 neuter 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>
+  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>
 
   </div>
 
@@ -81589,9 +81590,9 @@ function receiver(e) {
 
       <p>If any object is listed in <var title="">transfer</var> more
       than once, or any of the <code><a href=#transferable>Transferable</a></code> objects
-      listed in <var title="">transfer</var> have already been <a href=#transfer-a-transferable-object title="transfer a Transferable object">transfered</a> once
-      before, then throw a <code><a href=#datacloneerror>DataCloneError</a></code> exception and
-      abort these steps.</p>
+      listed in <var title="">transfer</var> are marked as <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neutered</a>, then
+      throw a <code><a href=#datacloneerror>DataCloneError</a></code> exception and abort these
+      steps.</p>
 
      </li>
 
@@ -81603,9 +81604,9 @@ function receiver(e) {
       object">transferring</a> the object to the
       <code><a href=#window>Window</a></code> object on which the method was invoked, and
       add a mapping from the old object to the new transferred object
-      to <var title="">transfer map</var>. If the objects are
-      <code><a href=#messageport>MessagePort</a></code> objects, also append the new
-      transferred object to the <var title="">new ports</var>
+      to <var title="">transfer map</var>. For each new
+      <code><a href=#messageport>MessagePort</a></code> object obtained in this manner, append
+      the new transferred object to the <var title="">new ports</var>
       array.</p>
 
      </li>
@@ -82013,7 +82014,8 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
 
   </ol><p id=transferMessagePort>To <a href=#transfer-a-transferable-object title="transfer a Transferable
   object">transfer</a> a <code><a href=#messageport>MessagePort</a></code> object <var title="">old</var> to a new owner <var title="">owner</var>, a user
-  agent must <a href=#clone-a-port title="clone a port">clone</a> the <var title="">old</var> object with the cloned being owned by <var title="">owner</var>, and must return the resulting object.</p>
+  agent must <a href=#clone-a-port title="clone a port">clone</a> the <var title="">old</var> object with the clone being owned by <var title="">owner</var>, thus obtaining <var title="">new</var>, must
+  <a href=#concept-transferable-neutered title=concept-Transferable-neutered>neuter</a> the <var title="">old</var> port, and must finally return <var title="">new</var>.</p>
 
   <hr><!-- v2-onclose
   <p>The <dfn title="dom-MessagePort-active"><code>active</code></dfn>

source

@@ -8895,9 +8895,11 @@ interface <dfn>Transferable</dfn> { };</pre>
   <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 neuter 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>
+  type, and will permanently <dfn
+  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>
 
   </div>
 
@@ -92447,10 +92449,10 @@ function receiver(e) {
 
       <p>If any object is listed in <var title="">transfer</var> more
       than once, or any of the <code>Transferable</code> objects
-      listed in <var title="">transfer</var> have already been <span
-      title="transfer a Transferable object">transfered</span> once
-      before, then throw a <code>DataCloneError</code> exception and
-      abort these steps.</p>
+      listed in <var title="">transfer</var> are marked as <span
+      title="concept-Transferable-neutered">neutered</span>, then
+      throw a <code>DataCloneError</code> exception and abort these
+      steps.</p>
 
      </li>
 
@@ -92462,9 +92464,9 @@ function receiver(e) {
       object">transferring</span> the object to the
       <code>Window</code> object on which the method was invoked, and
       add a mapping from the old object to the new transferred object
-      to <var title="">transfer map</var>. If the objects are
-      <code>MessagePort</code> objects, also append the new
-      transferred object to the <var title="">new ports</var>
+      to <var title="">transfer map</var>. For each new
+      <code>MessagePort</code> object obtained in this manner, append
+      the new transferred object to the <var title="">new ports</var>
       array.</p>
 
      </li>
@@ -92933,8 +92935,11 @@ interface <dfn>MessageChannel</dfn> {
   object">transfer</span> a <code>MessagePort</code> object <var
   title="">old</var> to a new owner <var title="">owner</var>, a user
   agent must <span title="clone a port">clone</span> the <var
-  title="">old</var> object with the cloned being owned by <var
-  title="">owner</var>, and must return the resulting object.</p>
+  title="">old</var> object with the clone being owned by <var
+  title="">owner</var>, thus obtaining <var title="">new</var>, must
+  <span title="concept-Transferable-neutered">neuter</span> the <var
+  title="">old</var> port, and must finally return <var
+  title="">new</var>.</p>
 
   <hr>
 <!-- v2-onclose