Skip to content

Commit

Permalink
[] (0) Make postMessage() return void. (credit: js)
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@2117 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Aug 27, 2008
1 parent de16e2f commit 7f73af1
Show file tree
Hide file tree
Showing 2 changed files with 53 additions and 51 deletions.
56 changes: 28 additions & 28 deletions index
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@

<h1 id=html-5>HTML 5</h1>

<h2 class="no-num no-toc" id=draft>Draft Recommendation &mdash; 26 August
<h2 class="no-num no-toc" id=draft>Draft Recommendation &mdash; 27 August
2008</h2>

<p>You can take part in this work. <a
Expand Down Expand Up @@ -44859,8 +44859,8 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {

<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>();
Expand Down Expand Up @@ -44973,12 +44973,12 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {

<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
Expand Down Expand Up @@ -45020,7 +45020,7 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
</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
Expand All @@ -45046,20 +45046,34 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
<li>
<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
Expand All @@ -45071,20 +45085,6 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
href="#data4">data</a></code> attribute of the event have the value of
<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
Expand Down
48 changes: 25 additions & 23 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -42306,8 +42306,8 @@ interface <dfn>MessageChannel</dfn> {

<pre class="idl">interface <dfn>MessagePort</dfn> {
readonly attribute boolean <span title="dom-MessagePort-active">active</span>;
boolean <span title="dom-MessagePort-postMessage">postMessage</span>(in DOMString message);
boolean <span title="dom-MessagePort-postMessage">postMessage</span>(in DOMString message, in <span>MessagePort</span> messagePort);
void <span title="dom-MessagePort-postMessage">postMessage</span>(in DOMString message);
void <span title="dom-MessagePort-postMessage">postMessage</span>(in DOMString message, in <span>MessagePort</span> messagePort);
<span>MessagePort</span> <span title="dom-MessagePort-startConversation">startConversation</span>(in DOMString message);
void <span title="dom-MessagePort-start">start</span>();
void <span title="dom-MessagePort-close">close</span>();
Expand Down Expand Up @@ -42418,11 +42418,11 @@ interface <dfn>MessageChannel</dfn> {
argument, if any.</p></li>

<li><p>If the <var title="">source port</var> is not entangled with
another port, then return false and abort these steps.</p></li>
another port, then return and abort these steps.</p></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 title="">source port</var> is entangled.</p></li>
Expand Down Expand Up @@ -42461,7 +42461,7 @@ interface <dfn>MessageChannel</dfn> {

</li>

<li><p>Return true from the method, but continue with these
<li><p>Return from the method, but continue with these
steps.</p></li>

<li><p>Add the event to the <span>port message queue</span> of <var
Expand Down Expand Up @@ -42489,16 +42489,29 @@ interface <dfn>MessageChannel</dfn> {
<li><p>Let <var title="">message</var> be the method's first
argument.</p></li>

<li><p><span>Create a new <code>MessagePort</code> object</span>
owned by the <span>script execution context</span>, and let <var
title="">port1</var> be that object.</p></li>

<li><p>If the <var title="">source port</var> is not entangled with
another port, then return null and abort these steps.</p></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. -->
another port, then return <var title="">port1</var> and abort these
steps.</p></li>
<!-- 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.</p></li>

<li><p><span>Create a new <code>MessagePort</code> object</span>
owned by the owner of the <var title="">target port</var>, and let
<var title="">port2</var> be that object.</p></li>

<li><p><span>Entangle</span> the <var title="">port1</var> and <var
title="">port2</var> objects.</p></li>

<li><p>Create an event that uses the <code>MessageEvent</code>
interface, with the name <code
title="event-message">message</code>, which does not bubble, is
Expand All @@ -42507,17 +42520,6 @@ interface <dfn>MessageChannel</dfn> {
<li><p>Let the <code title="dom-MessageEvent-data">data</code>
attribute of the event have the value of <var
title="">message</var>, the method's first argument.</p></li>

<li><p><span>Create a new <code>MessagePort</code> object</span>
owned by the <span>script execution context</span>, and let <var
title="">port1</var> be that object.</p></li>

<li><p><span>Create a new <code>MessagePort</code> object</span>
owned by the owner of the <var title="">target port</var>, and let
<var title="">port2</var> be that object.</p></li>

<li><p><span>Entangle</span> the <var title="">port1</var> and <var
title="">port2</var> objects.</p></li>

<li><p>Let the <code
title="dom-MessageEvent-messagePort">messagePort</code> attribute
Expand Down

0 comments on commit 7f73af1

Please sign in to comment.