W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2009

html5/spec Overview.html,1.2338,1.2339

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 03 Jun 2009 19:28:02 +0000
To: public-html-commits@w3.org
Message-Id: <E1MBw82-0002al-Na@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv9754

Modified Files:
Log Message:
To avoid confusion, use different words for workers closing and for ports being disabled. (whatwg r3185)

Index: Overview.html
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2338
retrieving revision 1.2339
diff -u -d -r1.2338 -r1.2339
--- Overview.html	3 Jun 2009 09:41:21 -0000	1.2338
+++ Overview.html	3 Jun 2009 19:27:59 -0000	1.2339
@@ -52162,7 +52162,10 @@
   another (a symmetric relationship). Each <code><a href="#messageport">MessagePort</a></code>
   object also has a <a href="#task-source">task source</a> called the <dfn id="port-message-queue">port
   message queue</dfn>, initial empty. A <a href="#port-message-queue">port message
-  queue</a> can be open or closed, and is initially closed.</p>
+  queue</a> can be enabled or disabled, and is initially
+  disabled. Once enabled, a port can never be disabled again (though
+  messages in the queue can get moved to another queue or removed
+  altogether, which has much the same effect).</p>
   <p>When the user agent is to <dfn id="create-a-new-messageport-object">create a new
   <code>MessagePort</code> object</dfn> owned by a <a href="#script-s-global-object">script's
@@ -52210,7 +52213,7 @@
    of <var title="">original port</var> to the <a href="#port-message-queue">port message
    queue</a> of <var title="">new port</var>, if any, leaving the
    <var title="">new port</var>'s <a href="#port-message-queue">port message queue</a> in
-   its initial closed state.</li>
+   its initial disabled state.</li>
    <li><p><a href="#entangle">Entangle</a> the <var title="">remote port</var>
    and <var title="">new port</var> objects. The <var title="">original port</var> object will be disentangled by this
@@ -52356,10 +52359,10 @@
 --><hr><p>The <dfn id="dom-messageport-start" title="dom-MessagePort-start"><code>start()</code></dfn>
-  method must open its port's <a href="#port-message-queue">port message queue</a>, if it
-  is not already open.</p>
+  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 open, the
+  <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>
@@ -52381,7 +52384,7 @@
   <table><thead><tr><th><a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a> <th><a href="#event-handler-event-type">Event handler event type</a>
    <tbody><tr><td><dfn id="handler-messageport-onmessage" title="handler-MessagePort-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message"><a href="#event-message">message</a></code>
   </table><p>The first time a <code><a href="#messageport">MessagePort</a></code> object's <code title="handler-MessagePort-onmessage"><a href="#handler-messageport-onmessage">onmessage</a></code> DOM attribute
-  is set, the port's <a href="#port-message-queue">port message queue</a> must be opened,
+  is set, the port's <a href="#port-message-queue">port message queue</a> must be enabled,
   as if the <code title="dom-MessagePort-start"><a href="#dom-messageport-start">start()</a></code> method
   had been called.</p>
Received on Wednesday, 3 June 2009 19:28:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:09:22 UTC