html5/spec Overview.html,1.1289,1.1290

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv18053

Modified Files:
	Overview.html 
Log Message:
Make postMessage() return void. (credit: js) (whatwg r2117)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1289
retrieving revision 1.1290
diff -u -d -r1.1289 -r1.1290
--- Overview.html	26 Aug 2008 10:36:07 -0000	1.1289
+++ Overview.html	27 Aug 2008 09:49:58 -0000	1.1290
@@ -27,7 +27,7 @@
     for HTML and XHTML</h2>
 
    <h2 class="no-num no-toc" id=editors0><!-- "W3C Working Draft" -->
-    Editor's Draft <!--ZZZ-->26 August 2008</h2>
+    Editor's Draft <!--ZZZ-->27 August 2008</h2>
 
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
@@ -199,7 +199,7 @@
 
   <p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is
    the W3C working group responsible for this specification's progress along
-   the W3C Recommendation track. <!--ZZZ:--> This specification is the 26
+   the W3C Recommendation track. <!--ZZZ:--> This specification is the 27
    August 2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
   <!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST -->
   <!-- relationship to other work (required) -->
@@ -44867,8 +44867,8 @@
 
   <pre class=idl>interface <dfn id=messageport0>MessagePort</dfn> {
   readonly attribute boolean <a href="#active0" title=dom-MessagePort-active>active</a>;
-  boolean <a href="#postmessage2" title=dom-MessagePort-postMessage>postMessage</a>(in DOMString message);
-  boolean <a href="#postmessage2" title=dom-MessagePort-postMessage>postMessage</a>(in DOMString message, in <a href="#messageport0">MessagePort</a> messagePort);
+  void <a href="#postmessage2" title=dom-MessagePort-postMessage>postMessage</a>(in DOMString message);
+  void <a href="#postmessage2" title=dom-MessagePort-postMessage>postMessage</a>(in DOMString message, in <a href="#messageport0">MessagePort</a> messagePort);
   <a href="#messageport0">MessagePort</a> <a href="#startconversation" title=dom-MessagePort-startConversation>startConversation</a>(in DOMString message);
   void <a href="#start6" title=dom-MessagePort-start>start</a>();
   void <a href="#close3" title=dom-MessagePort-close>close</a>();
@@ -44981,12 +44981,12 @@
 
    <li>
     <p>If the <var title="">source port</var> is not entangled with another
-     port, then return false and abort these steps.
+     port, then return and abort these steps.
    </li>
    <!-- we don't raise an exception because this can happen moment's
-   notice, but we return false so that the caller can check whether
-   the port was active at time of calling without a race
-   condition. -->
+   notice. listen to onclose if you want to know when things start
+   going wonky. (We don't return false because if the port is _about_
+   to be closed, the message might not be listened for anyway.) -->
 
    <li>
     <p>Let <var title="">target port</var> be the port with which <var
@@ -45028,7 +45028,7 @@
     </ol>
 
    <li>
-    <p>Return true from the method, but continue with these steps.
+    <p>Return from the method, but continue with these steps.
 
    <li>
     <p>Add the event to the <a href="#port-message">port message queue</a> of
@@ -45055,20 +45055,34 @@
     <p>Let <var title="">message</var> be the method's first argument.
 
    <li>
+    <p><a href="#create">Create a new <code>MessagePort</code> object</a>
+     owned by the <a href="#script2">script execution context</a>, and let
+     <var title="">port1</var> be that object.
+
+   <li>
     <p>If the <var title="">source port</var> is not entangled with another
-     port, then return null and abort these steps.
+     port, then return <var title="">port1</var> and abort these steps.
    </li>
-   <!--
-   we don't raise an exception because this can happen moment's
-   notice, but we return false so that the caller can check whether
-   the port was active at time of calling without a race
-   condition. -->
+   <!-- we don't raise an exception because this can happen moment's
+   notice. listen to onclose if you want to know when things start
+   going wonky. (We don't return null because then we'd end up with
+   null derefs. better to just let the likely next postMessage call
+   fall on the floor) -->
 
    <li>
     <p>Let <var title="">target port</var> be the port with which <var
      title="">source port</var> is entangled.
 
    <li>
+    <p><a href="#create">Create a new <code>MessagePort</code> object</a>
+     owned by the owner of the <var title="">target port</var>, and let <var
+     title="">port2</var> be that object.
+
+   <li>
+    <p><a href="#entangle">Entangle</a> the <var title="">port1</var> and
+     <var title="">port2</var> objects.
+
+   <li>
     <p>Create an event that uses the <code><a
      href="#messageevent">MessageEvent</a></code> interface, with the name
      <code title=event-message><a href="#message2">message</a></code>, which
@@ -45080,20 +45094,6 @@
      <var title="">message</var>, the method's first argument.
 
    <li>
-    <p><a href="#create">Create a new <code>MessagePort</code> object</a>
-     owned by the <a href="#script2">script execution context</a>, and let
-     <var title="">port1</var> be that object.
-
-   <li>
-    <p><a href="#create">Create a new <code>MessagePort</code> object</a>
-     owned by the owner of the <var title="">target port</var>, and let <var
-     title="">port2</var> be that object.
-
-   <li>
-    <p><a href="#entangle">Entangle</a> the <var title="">port1</var> and
-     <var title="">port2</var> objects.
-
-   <li>
     <p>Let the <code title=dom-MessageEvent-messagePort><a
      href="#messageport">messagePort</a></code> attribute of the event be
      <var title="">port2</var>.

Received on Wednesday, 27 August 2008 09:50:36 UTC