- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 15 Jul 2008 10:40:39 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv26526
Modified Files:
Overview.html
Log Message:
Define what happens when you call the postMessage() method with a null port. (whatwg r1875)
Index: Overview.html
===================================================================
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:41:16 UTC