- From: CVS User ihickson <cvsmail@w3.org>
- Date: Mon, 26 Aug 2013 18:03:01 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/postmsg In directory roscoe:/tmp/cvs-serv9397 Modified Files: Overview.html Log Message: Reorganise the stuff about port message queues to be clearer. (whatwg r8154) --- /sources/public/html5/postmsg/Overview.html 2013/08/26 17:59:48 1.150 +++ /sources/public/html5/postmsg/Overview.html 2013/08/26 18:03:01 1.151 @@ -1233,12 +1233,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 <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> + <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 the <span title="concept-task">tasks</span> 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 <span>task source</span>. When a <span title="concept-task">task</span> 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 + <span>task source</span>. When a <span title="concept-task">task</span> 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 <span>event loop</span>. (The @@ -1452,13 +1461,6 @@ </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 agent to disentangle the two ports. If the method is called on a port that is not entangled, then the
Received on Monday, 26 August 2013 18:03:02 UTC