W3C home > Mailing lists > Public > public-html-diffs@w3.org > October 2011

hixie: Clarify that you can transfer a port more than once by avoiding confusing terminology that suggested otherwise. (whatwg r6653)

From: poot <cvsmail@w3.org>
Date: Fri, 07 Oct 2011 18:01:59 -0400
To: public-html-diffs@w3.org
Message-Id: <E1RCIUQ-0005Xk-VJ@jay.w3.org>
hixie: Clarify that you can transfer a port more than once by avoiding
confusing terminology that suggested otherwise. (whatwg r6653)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5334&r2=1.5335&f=h
http://html5.org/tools/web-apps-tracker?from=6652&to=6653

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5334
retrieving revision 1.5335
diff -u -d -r1.5334 -r1.5335
--- Overview.html	7 Oct 2011 21:45:06 -0000	1.5334
+++ Overview.html	7 Oct 2011 22:01:40 -0000	1.5335
@@ -7448,9 +7448,10 @@
   <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><p>The following <code><a href="#transferable">Transferable</a></code> types exist:<ul class="brief"><li><code>MessagePort</code>
Received on Friday, 7 October 2011 22:02:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 7 October 2011 22:02:06 GMT