- From: CVS User ihickson <cvsmail@w3.org>
- Date: Mon, 27 Jan 2014 23:08:52 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/postmsg
In directory roscoe:/tmp/cvs-serv13154
Modified Files:
Overview.html
Log Message:
Update the spec to say what's exposed to workers: take 1 (whatwg r8425)
--- /sources/public/html5/postmsg/Overview.html 2014/01/17 08:12:30 1.163
+++ /sources/public/html5/postmsg/Overview.html 2014/01/27 23:08:51 1.164
@@ -216,7 +216,7 @@
<h1>HTML5 Web Messaging</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-17-january-2014">Editor's Draft 17 January 2014</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-27-january-2014">Editor's Draft 27 January 2014</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/webmessaging/">http://www.w3.org/TR/webmessaging/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -348,7 +348,7 @@
</dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications
Working Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation track.
- This specification is the 17 January 2014 Editor's Draft.
+ This specification is the 27 January 2014 Editor's Draft.
</p>
@@ -488,13 +488,14 @@
<code><a href="#messageevent">MessageEvent</a></code> interface for their <code title="event-message">message</code>
events:</p>
- <pre class="idl">[Constructor(DOMString type, optional <a href="#messageeventinit">MessageEventInit</a> eventInitDict)]
+ <pre class="idl">[Constructor(DOMString type, optional <a href="#messageeventinit">MessageEventInit</a> eventInitDict), Exposed=Window,Worker]
interface <dfn id="messageevent">MessageEvent</dfn> : <span>Event</span> {
readonly attribute any <a href="#dom-messageevent-data" title="dom-MessageEvent-data">data</a>;
readonly attribute DOMString <a href="#dom-messageevent-origin" title="dom-MessageEvent-origin">origin</a>;
readonly attribute DOMString <a href="#dom-messageevent-lasteventid" title="dom-MessageEvent-lastEventId">lastEventId</a>;
readonly attribute DOMString <a href="#dom-messageevent-channel" title="dom-MessageEvent-channel">channel</a>;
- readonly attribute (<span>WindowProxy</span> or <a href="#messageport">MessagePort</a>)? <a href="#dom-messageevent-source" title="dom-MessageEvent-source">source</a>;
+ [Exposed=Window] readonly attribute (<span>WindowProxy</span> or <a href="#messageport">MessagePort</a>)? <a href="#dom-messageevent-source" title="dom-MessageEvent-source">source</a>;
+ [Exposed=Worker] readonly attribute <a href="#messageport">MessagePort</a>? <a href="#dom-messageevent-source" title="dom-MessageEvent-source">source</a>;
readonly attribute <a href="#messageport">MessagePort</a>[]? <a href="#dom-messageevent-ports" title="dom-MessageEvent-ports">ports</a>;
};
@@ -1013,7 +1014,7 @@
<h3 id="message-channels"><span class="secno">5.2 </span>Message channels</h3>
- <pre class="idl">[<a href="#dom-messagechannel" title="dom-MessageChannel">Constructor</a>]
+ <pre class="idl">[<a href="#dom-messagechannel" title="dom-MessageChannel">Constructor</a>, Exposed=Window,Worker]
interface <dfn id="messagechannel">MessageChannel</dfn> {
readonly attribute <a href="#messageport">MessagePort</a> <a href="#dom-channel-port1" title="dom-channel-port1">port1</a>;
readonly attribute <a href="#messageport">MessagePort</a> <a href="#dom-channel-port2" title="dom-channel-port2">port2</a>;
@@ -1078,7 +1079,8 @@
<p>Each channel has two message ports. Data sent through one port is received by the other port,
and vice versa.</p>
- <pre class="idl">interface <dfn id="messageport">MessagePort</dfn> : <span>EventTarget</span> {
+ <pre class="idl">[Exposed=Window,Worker]
+interface <dfn id="messageport">MessagePort</dfn> : <span>EventTarget</span> {
void <a href="#dom-messageport-postmessage" title="dom-MessagePort-postMessage">postMessage</a>(any message, optional sequence<<span>Transferable</span>> transfer);
void <a href="#dom-messageport-start" title="dom-MessagePort-start">start</a>();
void <a href="#dom-messageport-close" title="dom-MessagePort-close">close</a>();
@@ -1129,8 +1131,9 @@
initially be false, and an <dfn id="concept-port-owner" title="concept-port-owner">owner</dfn>, which is a <span>settings
object</span> set when the object is created, as described below.</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>. All <span title="concept-task">tasks</span> <span title="queue a task">queued</span> on the <a href="#port-message-queue">port
+ it as one of its <span title="task source">task sources</span>. When a port's <a href="#concept-port-owner" title="concept-port-owner">owner</a> specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, all <span title="concept-task">tasks</span> <span title="queue a task">queued</span> on its <a href="#port-message-queue">port
message queue</a> must be associated with the <span>responsible document</span> specified by
the port's <a href="#concept-port-owner" title="concept-port-owner">owner</a>.</p>
@@ -1203,15 +1206,19 @@
<li><p>Set <var title="">new port</var>'s <a href="#has-been-shipped">has been shipped</a> flag to true.</li>
+
<li><p>Move all the <span title="concept-task">tasks</span> that are to fire <code title="event-message">message</code> events in the <a href="#port-message-queue">port message queue</a> 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 disabled state, and reassociating the moved <span title="concept-task">tasks</span> with the <span>responsible document</span> specified by <var title="">new port</var>'s <a href="#concept-port-owner" title="concept-port-owner">owner</a>.</li>
+ in its initial disabled state, and, if the <var title="">new port</var>'s <a href="#concept-port-owner" title="concept-port-owner">owner</a>
+ specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, associating the moved <span title="concept-task">tasks</span> with the <span>responsible document</span> specified by <var title="">new port</var>'s <a href="#concept-port-owner" title="concept-port-owner">owner</a>.</li>
+
<li><p>If <var title="">original port</var> is <a href="#related-to-an-ill-fated-port">related to an ill-fated port</a>, then
create a <span title="concept-task">task</span> that <span title="fire a simple event">fires a
simple event</span> named <code title="event-error">error</code> at the <var title="">new
port</var>, and add the <span title="concept-task">task</span> to the <a href="#port-message-queue">port message
- queue</a> of <var title="">new port</var>. The <span title="concept-task">task</span> must
+ queue</a> of <var title="">new port</var>. If the <var title="">new port</var>'s <a href="#concept-port-owner" title="concept-port-owner">owner</a>
+ specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, the <span title="concept-task">task</span> must
be associated with the <span>responsible document</span> specified by <var title="">new
port</var>'s <a href="#concept-port-owner" title="concept-port-owner">owner</a>.</li>
@@ -1397,9 +1404,11 @@
<li><p>Mark <var title="">target port</var> as being a <dfn id="related-to-an-ill-fated-port">related to an ill-fated
port</dfn>.</li>
+
<li><p>Create a <span title="concept-task">task</span> that <span title="fire a simple
event">fires a simple event</span> named <code title="event-error">error</code> at <var title="">target port</var>, and add the <span title="concept-task">task</span> to the
- <a href="#port-message-queue">port message queue</a> of <var title="">target port</var>. The <span title="concept-task">task</span> must be associated with the <span>responsible document</span>
+ <a href="#port-message-queue">port message queue</a> of <var title="">target port</var>. If the <var title="">new port</var>'s <a href="#concept-port-owner" title="concept-port-owner">owner</a>
+ specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, the <span title="concept-task">task</span> must be associated with the <span>responsible document</span>
specified by <var title="">source port</var>'s <a href="#concept-port-owner" title="concept-port-owner">owner</a>.</li>
<li><p>Disentangle the two ports.</li>
@@ -1440,7 +1449,8 @@
they stop being relevant, while still allowing scripts to iterate over the
<code><a href="#messageport">MessagePort</a></code> objects.</p>
- <pre class="idl">[<a href="#dom-portcollection" title="dom-PortCollection">Constructor</a>] interface <dfn id="portcollection">PortCollection</dfn> {
+ <pre class="idl">[<a href="#dom-portcollection" title="dom-PortCollection">Constructor</a>, Exposed=Window,Worker]
+interface <dfn id="portcollection">PortCollection</dfn> {
void <a href="#dom-portcollection-add" title="dom-PortCollection-add">add</a>(<a href="#messageport">MessagePort</a> port);
void <a href="#dom-portcollection-remove" title="dom-PortCollection-remove">remove</a>(<a href="#messageport">MessagePort</a> port);
void <a href="#dom-portcollection-clear" title="dom-PortCollection-clear">clear</a>();
Received on Monday, 27 January 2014 23:08:56 UTC