postmsg; hixie: Move the Web to a world where things that implement EventTarget just inherit from it. I, for one, now welcome our new EventTarget overlords. (whatwg r6378)

postmsg; hixie: Move the Web to a world where things that implement
EventTarget just inherit from it. I, for one, now welcome our new
EventTarget overlords. (whatwg r6378)

http://dev.w3.org/cvsweb/html5/postmsg/Overview.html?r1=1.91&r2=1.92&f=h
http://html5.org/tools/web-apps-tracker?from=6377&to=6378

===================================================================
RCS file: /sources/public/html5/postmsg/Overview.html,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -d -r1.91 -r1.92
--- Overview.html 28 Jul 2011 01:29:15 -0000 1.91
+++ Overview.html 5 Aug 2011 23:44:01 -0000 1.92
@@ -213,7 +213,7 @@
 
    <h1>HTML5 Web Messaging</h1>
    
-   <h2 class="no-num no-toc" id="editor-s-draft-28-july-2011">Editor's Draft 28 July 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-5-august-2011">Editor's Draft 5 August 2011</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/webmessaging/">http://www.w3.org/TR/webmessaging/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -315,7 +315,7 @@
   </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
-  This specification is the 28 July 2011 Editor's Draft.
+  This specification is the 5 August 2011 Editor's Draft.
   </p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
   February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of
   any patent disclosures</a> made in connection with the deliverables
@@ -805,14 +805,13 @@
   <code><a href="#messagechannel">MessageChannel</a></code> object was created.</p>
 
   </div><h3 id="message-ports"><span class="secno">5.3 </span>Message ports</h3><p>Each channel has two message ports. Data sent through one port is
-  received by the other port, and vice versa.<pre class="idl">interface <dfn id="messageport">MessagePort</dfn> {
+  received by the other port, and vice versa.<pre class="idl">interface <dfn id="messageport">MessagePort</dfn> : <span>EventTarget</span> {
   void <a href="#dom-messageport-postmessage" title="dom-MessagePort-postMessage">postMessage</a>(in any message, in optional sequence&lt;<span>Transferable</span>&gt; transfer);  void <a href="#dom-messageport-start" title="dom-MessagePort-start">start</a>();
   void <a href="#dom-messageport-close" title="dom-MessagePort-close">close</a>();
 
   // event handlers
            attribute <span>Function</span>? <a href="#handler-messageport-onmessage" title="handler-MessagePort-onmessage">onmessage</a>;
 };
-<a href="#messageport">MessagePort</a> implements <span>EventTarget</span>;
 <a href="#messageport">MessagePort</a> implements <span>Transferable</span>;</pre><dl class="domintro"><dt><var title="">port</var> . <code title="dom-MessagePort-postMessage"><a href="#dom-messageport-postmessage">postMessage</a></code>(<var title="">message</var> [, <var title="">transfer</var>] )</dt>
 
    <dd>

Received on Friday, 5 August 2011 23:44:24 UTC