W3C home > Mailing lists > Public > public-html-diffs@w3.org > March 2010

postmsg; hixie: Move the 'ports' argument to the end of postMessage() instead of in the middle. (whatwg r4870)

From: poot <cvsmail@w3.org>
Date: Fri, 26 Mar 2010 08:57:39 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100325235739.BCAD92BC46@toro.w3.mag.keio.ac.jp>
postmsg; hixie: Move the 'ports' argument to the end of postMessage()
instead of in the middle. (whatwg r4870)

http://dev.w3.org/cvsweb/html5/postmsg/Overview.html?r1=1.25&r2=1.26&f=h
http://html5.org/tools/web-apps-tracker?from=4869&to=4870

===================================================================
RCS file: /sources/public/html5/postmsg/Overview.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- Overview.html	17 Mar 2010 23:50:50 -0000	1.25
+++ Overview.html	25 Mar 2010 23:57:24 -0000	1.26
@@ -283,7 +283,7 @@
    <h1>HTML5 Web Messaging</h1>
    <h2 class="no-num no-toc" id="generatedID"></h2>
 
-   <h2 class="no-num no-toc" id="editor-s-draft-17-march-2010">Editor's Draft 17 March 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-25-march-2010">Editor's Draft 25 March 2010</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/postmsg/">http://www.w3.org/TR/postmsg/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -377,7 +377,7 @@
   specification's progress along the W3C Recommendation
   track.
 
-  This specification is the 17 March 2010 Editor's Draft.
+  This specification is the 25 March 2010 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>The contents of this specification are also part of <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/">a
   specification</a> published by the <a href="http://www.whatwg.org/">WHATWG</a>, which is available under a
   license that permits reuse of the specification text.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><!-- (this text is from the RDFa+HTML spec --><p>This specification is an extension to the HTML5 language. All
@@ -691,9 +691,9 @@
 
   <h3 id="posting-messages-with-message-ports"><span class="secno">3.4 </span>Posting messages with message ports</h3>
 
-  <p>When a script invokes the <dfn id="dom-window-postmessage-3" title="dom-window-postMessage-3"><code>postMessage(<var title="">message</var>, <var title="">ports</var>, <var title="">targetOrigin</var>)</code></dfn> method (with three
-  arguments) on a <code>Window</code> object, the user agent must
-  follow these steps:
+  <p>When a script invokes the <dfn id="dom-window-postmessage-3" title="dom-window-postMessage-3"><code>postMessage(<var title="">message</var>, <var title="">targetOrigin</var>, <var title="">ports</var>)</code></dfn> method (with three arguments) on
+  a <code>Window</code> object, the user agent must follow these
+  steps:
 
   <ol><!-- EXCEPT WHERE NOTED, THESE STEPS ARE IDENTICAL TO THE PREVIOUS SECTION --><!-- one exception is the use of -3 instead of -2 in the xrefs --><li>
 
@@ -823,7 +823,7 @@
   two-ways pipes, with a port at each end. Messages sent in one port
   are delivered at the other port, and vice-versa. Messages are
   asynchronous, and delivered as DOM events.<p>To create a connection (two "entangled" ports), the <code title="">MessageChannel()</code> constructor is called:<pre>var channel = new MessageChannel();</pre><p>One of the ports is kept as the local port, and the other port is
-  sent to the remote code, e.g. using <code title="dom-window-postMessage-3"><a href="#dom-window-postmessage-3">postMessage()</a></code>:<pre>otherWindow.postMessage('hello', [channel.port2], 'http://example.com');</pre><p>To send messages, the <code title="dom-MessagpePort-postMessage">postMessage()</code> method on
+  sent to the remote code, e.g. using <code title="dom-window-postMessage-3"><a href="#dom-window-postmessage-3">postMessage()</a></code>:<pre>otherWindow.postMessage('hello', 'http://example.com', [channel.port2]);</pre><p>To send messages, the <code title="dom-MessagpePort-postMessage">postMessage()</code> method on
   the port is used:<pre>channel.port1.postMessage('hello');</pre><p>To receive messages, one listens to <code title="event-message"><a href="#event-message">message</a></code> events:<pre>channel.port1.onmessage = handleMessage;
 function handleMessage(event) {
   // message is in event.data
Received on Thursday, 25 March 2010 23:58:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:18 GMT