- From: CVS User ihickson <cvsmail@w3.org>
- Date: Tue, 05 Feb 2013 22:23:49 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/postmsg
In directory roscoe:/tmp/cvs-serv29626
Modified Files:
Overview.html
Log Message:
Cleanup (whatwg r7695)
--- /sources/public/html5/postmsg/Overview.html 2013/02/05 20:33:04 1.136
+++ /sources/public/html5/postmsg/Overview.html 2013/02/05 22:23:49 1.137
@@ -1228,16 +1228,13 @@
</dl><div class="impl">
- <p>Each <code><a href="#messageport">MessagePort</a></code> object can be entangled with
- another (a symmetric relationship). Each <code><a href="#messageport">MessagePort</a></code>
- object also has a <span>task source</span> called the <dfn id="port-message-queue">port
- message queue</dfn>, initially empty. A <a href="#port-message-queue">port message
- 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).
- 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>Each <code><a href="#messageport">MessagePort</a></code> object can be entangled with another (a symmetric relationship).
+ Each <code><a href="#messageport">MessagePort</a></code> object also has a <span>task source</span> called the <dfn id="port-message-queue">port
+ message queue</dfn>, initially empty. A <a href="#port-message-queue">port message 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). 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>Each <span>event loop</span> has a <span>task source</span> called the <dfn id="unshipped-port-message-queue">unshipped port
message queue</dfn>. This is a virtual <span>task source</span>: it must act as if it contained
@@ -1256,15 +1253,12 @@
is true, its <a href="#port-message-queue">port message queue</a> acts as a first-class <span>task source</span>,
unaffected to any <a href="#unshipped-port-message-queue">unshipped port message queue</a>.</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 <span>script's
- global object</span> object <var title="">owner</var>, it must
- instantiate a new <code><a href="#messageport">MessagePort</a></code> object, and let its owner
- be <var title="">owner</var>.</p>
-
- <p>When the user agent is to <dfn id="entangle">entangle</dfn> two
- <code><a href="#messageport">MessagePort</a></code> objects, it must run the following
- steps:</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
+ <span>script's global object</span> object <var title="">owner</var>, it must instantiate a new
+ <code><a href="#messageport">MessagePort</a></code> object, and let its owner be <var title="">owner</var>.</p>
+
+ <p>When the user agent is to <dfn id="entangle">entangle</dfn> two <code><a href="#messageport">MessagePort</a></code> objects, it must run
+ the following steps:</p>
<ol><li>
@@ -1448,29 +1442,24 @@
<li><p>Add the event to the <a href="#port-message-queue">port message queue</a> of <var title="">target port</var>.</li>
- </ol><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
- <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>
-
-
- <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 agents to
- disentangle the two ports. If the method is called on a port that is
- not entangled, then the method must do nothing.</p>
-
- <hr><p>The following are the <span>event handlers</span> (and their
- corresponding <span title="event handler event type">event handler
- event types</span>) that must be supported, as IDL attributes, by
- all objects implementing the <code><a href="#messageport">MessagePort</a></code> interface:</p>
+ </ol><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 <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>
+
+ <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 agents to
+ disentangle the two ports. If the method is called on a port that is not entangled, then the
+ method must do nothing.</p>
+
+ <hr><p>The following are the <span>event handlers</span> (and their corresponding <span title="event
+ handler event type">event handler event types</span>) that must be supported, as IDL attributes,
+ by all objects implementing the <code><a href="#messageport">MessagePort</a></code> interface:</p>
<table><thead><tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<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>
Received on Tuesday, 5 February 2013 22:23:50 UTC