[html5] r8154 - [e] (0) Reorganise the stuff about port message queues to be clearer. Affected t [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-08-26 11:02:57 -0700 (Mon, 26 Aug 2013)
New Revision: 8154

Modified:
   complete.html
   index
   source
Log:
[e] (0) Reorganise the stuff about port message queues to be clearer.
Affected topics: DOM APIs

Modified: complete.html
===================================================================
--- complete.html	2013-08-26 17:59:42 UTC (rev 8153)
+++ complete.html	2013-08-26 18:02:57 UTC (rev 8154)
@@ -83400,12 +83400,21 @@
   same effect). A <code><a href=#messageport>MessagePort</a></code> also has a <dfn id=has-been-shipped>has been shipped</dfn> flag. It must
   initially be false.</p>
 
+  <p>When a port's <a href=#port-message-queue>port message queue</a> is enabled, the <a href=#event-loop>event loop</a> must use
+  it as one of its <a href=#task-source title="task source">task sources</a>.</p>
+
+  <p class=note>If the <code><a href=#document>Document</a></code> of the port's event listeners' <a href="#script's-global-object" title="script's
+  global object">global object</a> is not <a href=#fully-active>fully active</a>, then the messages are
+  lost.</p> <!-- because of the jump-to-entry-point algorithm first step -->
+
   <p>Each <a href=#event-loop>event loop</a> has a <a href=#task-source>task source</a> called the <dfn id=unshipped-port-message-queue>unshipped port
   message queue</dfn>. This is a virtual <a href=#task-source>task source</a>: it must act as if it contained
   the <a href=#concept-task title=concept-task>tasks</a> of each <a href=#port-message-queue>port message queue</a> of each
-  <code><a href=#messageport>MessagePort</a></code> whose <a href=#has-been-shipped>has been shipped</a> flag is false and whose <a href=#port-message-queue>port message queue</a> is enabled, in the order in which
-  they were added to their respective <a href=#task-source>task source</a>. When a <a href=#concept-task title=concept-task>task</a> would be removed from the <a href=#unshipped-port-message-queue>unshipped port message
-  queue</a>, it must instead be removed from its <a href=#port-message-queue>port message queue</a>.</p>
+  <code><a href=#messageport>MessagePort</a></code> whose <a href=#has-been-shipped>has been shipped</a> flag is false and whose <a href=#port-message-queue>port
+  message queue</a> is enabled, in the order in which they were added to their respective
+  <a href=#task-source>task source</a>. When a <a href=#concept-task title=concept-task>task</a> would be removed from the
+  <a href=#unshipped-port-message-queue>unshipped port message queue</a>, it must instead be removed from its <a href=#port-message-queue>port message
+  queue</a>.</p>
 
   <p>When a <code><a href=#messageport>MessagePort</a></code>'s <a href=#has-been-shipped>has been shipped</a> flag is false, its <a href=#port-message-queue>port
   message queue</a> must be ignored for the purposes of the <a href=#event-loop>event loop</a>. (The
@@ -83689,13 +83698,6 @@
 --><hr><p>The <dfn id=dom-messageport-start title=dom-MessagePort-start><code>start()</code></dfn> method must enable its port's
   <a href=#port-message-queue>port message queue</a>, if it is not already enabled.</p>
 
-  <p>When a port's <a href=#port-message-queue>port message queue</a> is enabled, the <a href=#event-loop>event loop</a> must use
-  it as one of its <a href=#task-source title="task source">task sources</a>.</p>
-
-  <p class=note>If the <code><a href=#document>Document</a></code> of the port's event listeners' <a href="#script's-global-object" title="script's
-  global object">global object</a> is not <a href=#fully-active>fully active</a>, then the messages are
-  lost.</p> <!-- because of the jump-to-entry-point algorithm first step -->
-
   <hr><p>The <dfn id=dom-messageport-close title=dom-MessagePort-close><code>close()</code></dfn> method, when called on a port
   <var title="">local port</var> that is entangled with another port, must cause the user agent to
   disentangle the two ports. If the method is called on a port that is not entangled, then the

Modified: index
===================================================================
--- index	2013-08-26 17:59:42 UTC (rev 8153)
+++ index	2013-08-26 18:02:57 UTC (rev 8154)
@@ -83400,12 +83400,21 @@
   same effect). A <code><a href=#messageport>MessagePort</a></code> also has a <dfn id=has-been-shipped>has been shipped</dfn> flag. It must
   initially be false.</p>
 
+  <p>When a port's <a href=#port-message-queue>port message queue</a> is enabled, the <a href=#event-loop>event loop</a> must use
+  it as one of its <a href=#task-source title="task source">task sources</a>.</p>
+
+  <p class=note>If the <code><a href=#document>Document</a></code> of the port's event listeners' <a href="#script's-global-object" title="script's
+  global object">global object</a> is not <a href=#fully-active>fully active</a>, then the messages are
+  lost.</p> <!-- because of the jump-to-entry-point algorithm first step -->
+
   <p>Each <a href=#event-loop>event loop</a> has a <a href=#task-source>task source</a> called the <dfn id=unshipped-port-message-queue>unshipped port
   message queue</dfn>. This is a virtual <a href=#task-source>task source</a>: it must act as if it contained
   the <a href=#concept-task title=concept-task>tasks</a> of each <a href=#port-message-queue>port message queue</a> of each
-  <code><a href=#messageport>MessagePort</a></code> whose <a href=#has-been-shipped>has been shipped</a> flag is false and whose <a href=#port-message-queue>port message queue</a> is enabled, in the order in which
-  they were added to their respective <a href=#task-source>task source</a>. When a <a href=#concept-task title=concept-task>task</a> would be removed from the <a href=#unshipped-port-message-queue>unshipped port message
-  queue</a>, it must instead be removed from its <a href=#port-message-queue>port message queue</a>.</p>
+  <code><a href=#messageport>MessagePort</a></code> whose <a href=#has-been-shipped>has been shipped</a> flag is false and whose <a href=#port-message-queue>port
+  message queue</a> is enabled, in the order in which they were added to their respective
+  <a href=#task-source>task source</a>. When a <a href=#concept-task title=concept-task>task</a> would be removed from the
+  <a href=#unshipped-port-message-queue>unshipped port message queue</a>, it must instead be removed from its <a href=#port-message-queue>port message
+  queue</a>.</p>
 
   <p>When a <code><a href=#messageport>MessagePort</a></code>'s <a href=#has-been-shipped>has been shipped</a> flag is false, its <a href=#port-message-queue>port
   message queue</a> must be ignored for the purposes of the <a href=#event-loop>event loop</a>. (The
@@ -83689,13 +83698,6 @@
 --><hr><p>The <dfn id=dom-messageport-start title=dom-MessagePort-start><code>start()</code></dfn> method must enable its port's
   <a href=#port-message-queue>port message queue</a>, if it is not already enabled.</p>
 
-  <p>When a port's <a href=#port-message-queue>port message queue</a> is enabled, the <a href=#event-loop>event loop</a> must use
-  it as one of its <a href=#task-source title="task source">task sources</a>.</p>
-
-  <p class=note>If the <code><a href=#document>Document</a></code> of the port's event listeners' <a href="#script's-global-object" title="script's
-  global object">global object</a> is not <a href=#fully-active>fully active</a>, then the messages are
-  lost.</p> <!-- because of the jump-to-entry-point algorithm first step -->
-
   <hr><p>The <dfn id=dom-messageport-close title=dom-MessagePort-close><code>close()</code></dfn> method, when called on a port
   <var title="">local port</var> that is entangled with another port, must cause the user agent to
   disentangle the two ports. If the method is called on a port that is not entangled, then the

Modified: source
===================================================================
--- source	2013-08-26 17:59:42 UTC (rev 8153)
+++ source	2013-08-26 18:02:57 UTC (rev 8154)
@@ -93034,13 +93034,21 @@
   same effect). A <code>MessagePort</code> also has a <dfn>has been shipped</dfn> flag. It must
   initially be false.</p>
 
+  <p>When a port's <span>port message queue</span> is enabled, the <span>event loop</span> must use
+  it as one of its <span title="task source">task sources</span>.</p>
+
+  <p class="note">If the <code>Document</code> of the port's event listeners' <span title="script's
+  global object">global object</span> is not <span>fully active</span>, then the messages are
+  lost.</p> <!-- because of the jump-to-entry-point algorithm first step -->
+
   <p>Each <span>event loop</span> has a <span>task source</span> called the <dfn>unshipped port
   message queue</dfn>. This is a virtual <span>task source</span>: it must act as if it contained
   the <span title="concept-task">tasks</span> of each <span>port message queue</span> of each
-  <code>MessagePort</code> whose <span>has been shipped</span> flag is false and whose <span>port message queue</span> is enabled, in the order in which
-  they were added to their respective <span>task source</span>. When a <span
-  title="concept-task">task</span> would be removed from the <span>unshipped port message
-  queue</span>, it must instead be removed from its <span>port message queue</span>.</p>
+  <code>MessagePort</code> whose <span>has been shipped</span> flag is false and whose <span>port
+  message queue</span> is enabled, in the order in which they were added to their respective
+  <span>task source</span>. When a <span title="concept-task">task</span> would be removed from the
+  <span>unshipped port message queue</span>, it must instead be removed from its <span>port message
+  queue</span>.</p>
 
   <p>When a <code>MessagePort</code>'s <span>has been shipped</span> flag is false, its <span>port
   message queue</span> must be ignored for the purposes of the <span>event loop</span>. (The
@@ -93385,13 +93393,6 @@
   <p>The <dfn title="dom-MessagePort-start"><code>start()</code></dfn> method must enable its port's
   <span>port message queue</span>, if it is not already enabled.</p>
 
-  <p>When a port's <span>port message queue</span> is enabled, the <span>event loop</span> must use
-  it as one of its <span title="task source">task sources</span>.</p>
-
-  <p class="note">If the <code>Document</code> of the port's event listeners' <span title="script's
-  global object">global object</span> is not <span>fully active</span>, then the messages are
-  lost.</p> <!-- because of the jump-to-entry-point algorithm first step -->
-
   <hr>
 
   <p>The <dfn title="dom-MessagePort-close"><code>close()</code></dfn> method, when called on a port