[e] (0) To avoid confusion, use different words for workers closing a…

…nd for ports being disabled.

git-svn-id: http://svn.whatwg.org/webapps@3185 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -58072,7 +58072,10 @@ interface <dfn id=messageport>MessagePort</dfn> {
   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
@@ -58120,7 +58123,7 @@ interface <dfn id=messageport>MessagePort</dfn> {
    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
@@ -58266,10 +58269,10 @@ interface <dfn id=messageport>MessagePort</dfn> {
 
   </ol>
 --><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>
 
@@ -58291,7 +58294,7 @@ interface <dfn id=messageport>MessagePort</dfn> {
   <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>
 

source

@@ -68192,8 +68192,8 @@ XXX Once we resolve the style="" issue, address these:
 
    <li><p>If <var title="">worker global scope</var> is actually a
    <code>DedicatedWorkerGlobalScope</code> object (i.e. the worker is
-   a dedicated worker), then open the <span>port message queue</span>
-   of the worker's implicit port.</p></li>
+   a dedicated worker), then enable the <span>port message
+   queue</span> of the worker's implicit port.</p></li>
 
    <li>
 
@@ -68546,10 +68546,10 @@ interface <dfn>Worker</dfn> : <span>AbstractWorker</span> {
    <li><p>Return <var title="">worker</var>, and run the following
    steps asynchronously.</p></li>
 
-   <li><p>Open <var title="">inside port</var>'s <span>port message
+   <li><p>Enable <var title="">inside port</var>'s <span>port message
    queue</span>.</p></li>
 
-   <li><p>Open <var title="">outside port</var>'s <span>port message
+   <li><p>Enable <var title="">outside port</var>'s <span>port message
    queue</span>.</p></li>
 
    <li>
@@ -71514,7 +71514,10 @@ interface <dfn>MessagePort</dfn> {
   another (a symmetric relationship). Each <code>MessagePort</code>
   object also has a <span>task source</span> called the <dfn>port
   message queue</dfn>, initial empty. A <span>port message
-  queue</span> can be open or closed, and is initially closed.</p>
+  queue</span> 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>create a new
   <code>MessagePort</code> object</dfn> owned by a <span>script's
@@ -71574,7 +71577,7 @@ interface <dfn>MessagePort</dfn> {
    of <var title="">original port</var> to the <span>port message
    queue</span> of <var title="">new port</var>, if any, leaving the
    <var title="">new port</var>'s <span>port message queue</span> in
-   its initial closed state.</p></li>
+   its initial disabled state.</p></li>
 
    <li><p><span>Entangle</span> the <var title="">remote port</var>
    and <var title="">new port</var> objects. The <var
@@ -71744,10 +71747,10 @@ interface <dfn>MessagePort</dfn> {
   <hr>
 
   <p>The <dfn title="dom-MessagePort-start"><code>start()</code></dfn>
-  method must open its port's <span>port message queue</span>, if it
-  is not already open.</p>
+  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 open, the
+  <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>
 
@@ -71780,7 +71783,7 @@ interface <dfn>MessagePort</dfn> {
 
   <p>The first time a <code>MessagePort</code> object's <code
   title="handler-MessagePort-onmessage">onmessage</code> DOM attribute
-  is set, the port's <span>port message queue</span> must be opened,
+  is set, the port's <span>port message queue</span> must be enabled,
   as if the <code title="dom-MessagePort-start">start()</code> method
   had been called.</p>