[html5] r7892 - [e] (0) Let's try some more explanatory text Fixing https://www.w3.org/Bugs/Publ [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-06-03 17:08:11 -0700 (Mon, 03 Jun 2013)
New Revision: 7892

Modified:
   complete.html
   index
   source
Log:
[e] (0) Let's try some more explanatory text
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=21416
Affected topics: DOM APIs

Modified: complete.html
===================================================================
--- complete.html	2013-06-03 23:41:48 UTC (rev 7891)
+++ complete.html	2013-06-04 00:08:11 UTC (rev 7892)
@@ -256,7 +256,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 3 June 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 4 June 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -82374,11 +82374,21 @@
 
    </li>
 
-   <li><p>Associate the two ports to be entangled, so that they form
-   the two parts of a new channel. (There is no
-   <code><a href=#messagechannel>MessageChannel</a></code> object that represents this
-   channel.)</li>
+   <li>
 
+    <p>Associate the two ports to be entangled, so that they form the two parts of a new channel.
+    (There is no <code><a href=#messagechannel>MessageChannel</a></code> object that represents this channel.)</p>
+
+    <p>Two ports A and B that have gone through this step are now said to be entangled; one is
+    entangled to the other, and vice versa.</p>
+
+    <p class=note>While this specification describes this process as instantaneous,
+    implementations are more likely to implement it via message passing. As with all algorithms, the
+    key is "merely" that the end result be indistinguishable, in a black-box sense, from the
+    specification.</p>
+
+   </li>
+
   </ol><p>When the user agent is to <dfn id=clone-a-port>clone a port</dfn> <var title="">original port</var>, with the clone being owned by <var title="">owner</var>, it must run the following steps, which return
   a new <code><a href=#messageport>MessagePort</a></code> object. These steps must be run
   atomically.</p>

Modified: index
===================================================================
--- index	2013-06-03 23:41:48 UTC (rev 7891)
+++ index	2013-06-04 00:08:11 UTC (rev 7892)
@@ -256,7 +256,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 3 June 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 4 June 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -82374,11 +82374,21 @@
 
    </li>
 
-   <li><p>Associate the two ports to be entangled, so that they form
-   the two parts of a new channel. (There is no
-   <code><a href=#messagechannel>MessageChannel</a></code> object that represents this
-   channel.)</li>
+   <li>
 
+    <p>Associate the two ports to be entangled, so that they form the two parts of a new channel.
+    (There is no <code><a href=#messagechannel>MessageChannel</a></code> object that represents this channel.)</p>
+
+    <p>Two ports A and B that have gone through this step are now said to be entangled; one is
+    entangled to the other, and vice versa.</p>
+
+    <p class=note>While this specification describes this process as instantaneous,
+    implementations are more likely to implement it via message passing. As with all algorithms, the
+    key is "merely" that the end result be indistinguishable, in a black-box sense, from the
+    specification.</p>
+
+   </li>
+
   </ol><p>When the user agent is to <dfn id=clone-a-port>clone a port</dfn> <var title="">original port</var>, with the clone being owned by <var title="">owner</var>, it must run the following steps, which return
   a new <code><a href=#messageport>MessagePort</a></code> object. These steps must be run
   atomically.</p>

Modified: source
===================================================================
--- source	2013-06-03 23:41:48 UTC (rev 7891)
+++ source	2013-06-04 00:08:11 UTC (rev 7892)
@@ -91886,11 +91886,21 @@
 
    </li>
 
-   <li><p>Associate the two ports to be entangled, so that they form
-   the two parts of a new channel. (There is no
-   <code>MessageChannel</code> object that represents this
-   channel.)</p></li>
+   <li>
 
+    <p>Associate the two ports to be entangled, so that they form the two parts of a new channel.
+    (There is no <code>MessageChannel</code> object that represents this channel.)</p>
+
+    <p>Two ports A and B that have gone through this step are now said to be entangled; one is
+    entangled to the other, and vice versa.</p>
+
+    <p class="note">While this specification describes this process as instantaneous,
+    implementations are more likely to implement it via message passing. As with all algorithms, the
+    key is "merely" that the end result be indistinguishable, in a black-box sense, from the
+    specification.</p>
+
+   </li>
+
   </ol>
 
   <p>When the user agent is to <dfn>clone a port</dfn> <var