[html5] r8153 - [giow] (1) Disabled port message queues shouldn't have their messages dispatched [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-08-26 10:59:42 -0700 (Mon, 26 Aug 2013)
New Revision: 8153

Modified:
   complete.html
   index
   source
Log:
[giow] (1) Disabled port message queues shouldn't have their messages dispatched when they're still unshipped, nor should they stall the entire message queueing mechanism.
Affected topics: DOM APIs

Modified: complete.html
===================================================================
--- complete.html	2013-08-22 05:23:56 UTC (rev 8152)
+++ complete.html	2013-08-26 17:59:42 UTC (rev 8153)
@@ -256,7 +256,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 22 August 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 26 August 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>
@@ -83403,7 +83403,7 @@
   <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, in the order in which
+  <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>
 

Modified: index
===================================================================
--- index	2013-08-22 05:23:56 UTC (rev 8152)
+++ index	2013-08-26 17:59:42 UTC (rev 8153)
@@ -256,7 +256,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard — Last Updated 22 August 2013</h2>
+    <h2 class="no-num no-toc">Living Standard — Last Updated 26 August 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>
@@ -83403,7 +83403,7 @@
   <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, in the order in which
+  <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>
 

Modified: source
===================================================================
--- source	2013-08-22 05:23:56 UTC (rev 8152)
+++ source	2013-08-26 17:59:42 UTC (rev 8153)
@@ -93037,7 +93037,7 @@
   <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, in the order in which
+  <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>