html5/spec Overview.html,1.1571,1.1572

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

Modified Files:
	Overview.html 
Log Message:
Remove startConversation() for now, as it is distracting in the worker discussions. May return in some form later. (whatwg r2400)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1571
retrieving revision 1.1572
diff -u -d -r1.1571 -r1.1572
--- Overview.html	13 Nov 2008 01:23:39 -0000	1.1571
+++ Overview.html	13 Nov 2008 01:45:11 -0000	1.1572
@@ -34765,8 +34765,8 @@
   received by the other port, and vice versa.<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>();
 
@@ -34878,50 +34878,67 @@
 
   </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><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
+  just strings.</p><!--
+  <hr>
+
+  <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:<ol><li><p>Let <var title="">message</var> be the method's first
-   argument.</li>
+  port</var>, it must run the following steps:</p>
 
-   <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>
+  <ol>
+
+   <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>When a port's <a href=#port-message-queue>port message queue</a> is open, contains
   an event, and its owner is <a href=#port-owner-available title="port owner

Received on Thursday, 13 November 2008 01:45:24 UTC