[] (0) Remove startConversation() for now, as it is distracting in th…

…e worker discussions. May return in some form later.

git-svn-id: http://svn.whatwg.org/webapps@2400 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -43374,8 +43374,8 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
   <pre class=idl>interface <dfn id=messageport>MessagePort</dfn> {
   readonly attribute boolean <a href=#dom-messageport-active title=dom-MessagePort-active>active</a>;
   void <a href=#dom-messageport-postmessage title=dom-MessagePort-postMessage>postMessage</a>(in DOMString message);
-  void <a href=#dom-messageport-postmessage title=dom-MessagePort-postMessage>postMessage</a>(in DOMString message, in <a href=#messageport>MessagePort</a> messagePort);
-  <a href=#messageport>MessagePort</a> <a href=#dom-messageport-startconversation title=dom-MessagePort-startConversation>startConversation</a>(in DOMString message);
+  void <a href=#dom-messageport-postmessage title=dom-MessagePort-postMessage>postMessage</a>(in DOMString message, in <a href=#messageport>MessagePort</a> messagePort);<!--
+  <span>MessagePort</span> <span title="dom-MessagePort-startConversation">startConversation</span>(in DOMString message);-->
   void <a href=#dom-messageport-start title=dom-MessagePort-start>start</a>();
   void <a href=#dom-messageport-close title=dom-MessagePort-close>close</a>();
 
@@ -43504,53 +43504,68 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
   </ol><p class=XXX>People often request the ability to send
   name/value pairs, arrays, and numbers using postMessage() instead of
   just strings.</p>
+<!--
+  <hr>
 
-  <hr><p>The <dfn id=dom-messageport-startconversation title=dom-MessagePort-startConversation><code>startConversation(<var title="">message</var>)</code></dfn> method is a convenience method
-  that simplifies create a new <code><a href=#messagechannel>MessageChannel</a></code> and
-  invoking <code title=dom-MessagePort-postMessage><a href=#dom-messageport-postmessage>postMessage()</a></code> with one of
+  <p>The <dfn
+  title="dom-MessagePort-startConversation"><code>startConversation(<var
+  title="">message</var>)</code></dfn> method is a convenience method
+  that simplifies create a new <code>MessageChannel</code> and
+  invoking <code
+  title="dom-MessagePort-postMessage">postMessage()</code> with one of
   the new ports. When invoked on a port <var title="">source
   port</var>, it must run the following steps:</p>
 
-  <ol><li><p>Let <var title="">message</var> be the method's first
-   argument.</li>
+  <ol>
 
-   <li><p><a href=#create-a-new-messageport-object>Create a new <code>MessagePort</code> object</a>
-   owned by the <a href=#script-execution-context>script execution context</a>, and let <var title="">port1</var> be that object.</li>
+   <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 <var title="">port1</var> and abort these
-   steps.</li>
-   <!-- we don't raise an exception because this can happen moment's
+   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) -->
+   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>
+   <var title="">source port</var> is entangled.</p></li>
 
-   <li><p><a href=#create-a-new-messageport-object>Create a new <code>MessagePort</code> object</a>
+   <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.</li>
+   <var title="">port2</var> be that object.</p></li>
 
-   <li><p><a href=#entangle>Entangle</a> the <var title="">port1</var> and <var title="">port2</var> objects.</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><a href=#messageevent>MessageEvent</a></code>
-   interface, with the name <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
-   cancelable, and has no default action.</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
+   cancelable, and has no default action.</p></li>
 
-   <li><p>Let the <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code>
-   attribute of the event have the value of <var title="">message</var>, the method's first argument.</li>
+   <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>Let the <code title=dom-MessageEvent-messagePort><a href=#dom-messageevent-messageport>messagePort</a></code> attribute
-   of the event be <var title="">port2</var>.</li>
+   <li><p>Let the <code
+   title="dom-MessageEvent-messagePort">messagePort</code> attribute
+   of the event be <var title="">port2</var>.</p></li>
 
    <li><p>Return <var title="">port1</var> from the method, but
-   continue with these steps.</li>
+   continue with these steps.</p></li>
 
-   <li><p>Add the event to the <a href=#port-message-queue>port message queue</a> of <var title="">target port</var>.</li>
+   <li><p>Add the event to the <span>port message queue</span> of <var
+   title="">target port</var>.</p></li>
 
-  </ol><hr><p>The <dfn id=dom-messageport-start title=dom-MessagePort-start><code>start()</code></dfn>
+  </ol>
+-->
+  <hr><p>The <dfn id=dom-messageport-start title=dom-MessagePort-start><code>start()</code></dfn>
   method must open its port's <a href=#port-message-queue>port message queue</a>, if it
   is not already open.</p>
 

source

@@ -49505,8 +49505,8 @@ interface <dfn>MessageChannel</dfn> {
   <pre class="idl">interface <dfn>MessagePort</dfn> {
   readonly attribute boolean <span title="dom-MessagePort-active">active</span>;
   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-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>();
 
@@ -49670,7 +49670,7 @@ interface <dfn>MessageChannel</dfn> {
   <p class="XXX">People often request the ability to send
   name/value pairs, arrays, and numbers using postMessage() instead of
   just strings.</p>
-
+<!--
   <hr>
 
   <p>The <dfn
@@ -49694,11 +49694,11 @@ interface <dfn>MessageChannel</dfn> {
    <li><p>If the <var title="">source port</var> is not entangled with
    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
+   <!- - 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) -->
+   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>
@@ -49730,7 +49730,7 @@ interface <dfn>MessageChannel</dfn> {
    title="">target port</var>.</p></li>
 
   </ol>
-
+-->
   <hr>
 
   <p>The <dfn title="dom-MessagePort-start"><code>start()</code></dfn>