spec/Overview.html 1.1064 1875 Define what happens when you call the po

Define what happens when you call the postMessage() method with a null
port. (whatwg r1875) (changed by: Ian Hickson)

Diffs for this change per section: 
  postMessage(message, messagePort, targetOrigin)
  http://people.w3.org/mike/diffs/html5/spec/Overview.1.1064.html#postmessage0

Current content per affected section: 
  http://dev.w3.org/html5/spec/Overview.html#postmessage0

Previously published WD content per affected section: 
  http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#postmessage0

Cumulative diff: http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1063&r2=1.1064&f=h

http://html5.org/tools/web-apps-tracker?from=1874&to=1875

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1063
retrieving revision 1.1064
diff -u -d -r1.1063 -r1.1064
--- Overview.html 15 Jul 2008 10:36:34 -0000 1.1063
+++ Overview.html 15 Jul 2008 10:40:36 -0000 1.1064
@@ -42444,6 +42444,12 @@
      of steps.</p>
 
    <li> <!-- NEW STEP -->
+    <p>If the <var title="">messagePort</var> argument is null, then act as
+     if the method had just been <a href="#postmessage"
+     title=dom-window-postMessage-2>called with two arguments</a>, <var
+     title="">message</var> and <var title="">targetOrigin</var>.</p>
+
+   <li> <!-- NEW STEP -->
     <p>Try to obtain a <var title="">new port</var> by <a href="#clone"
      title="clone a port">cloning</a> the <var title="">messagePort</var>
      argument with the <code><a href="#window">Window</a></code> object on
@@ -42510,8 +42516,8 @@
     <!-- XXX apply any body/window dispatch decisions here -->
   </ol>
 
-  <p class=note>These steps, with the exception of the second step and the
-   penultimate step, are identical to those in the previous section.</p>
+  <p class=note>These steps, with the exception of the second and third steps
+   and the penultimate step, are identical to those in the previous section.</p>
   <!-- XXX merge this section and the previous section when
   implementations have shipped postMessage(). Anne asked that these
   sections be kept separate so that implementors can avoid getting

Received on Tuesday, 15 July 2008 10:56:32 UTC