W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2008

html5/pubnotes Overview.html,1.316,1.317 Overview.src.html,1.308,1.309

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 18 Jul 2008 05:51:27 +0000
To: public-html-commits@w3.org
Message-Id: <E1KJisJ-00031O-RK@lionel-hutz.w3.org>

Update of /sources/public/html5/pubnotes
In directory hutz:/tmp/cvs-serv11361

Modified Files:
	Overview.html Overview.src.html 
Log Message:
1.1062 Define Message Channels and Ports. (whatwg r1873)


Index: Overview.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.316
retrieving revision 1.317
diff -u -d -r1.316 -r1.317
--- Overview.html	18 Jul 2008 05:12:06 -0000	1.316
+++ Overview.html	18 Jul 2008 05:51:25 -0000	1.317
@@ -36,7 +36,7 @@
         of the changes without necessarily needing to read the
         specification itself.</p>
     <div class="ednote"><h4 class="ednoteHeader">Editorial note</h4><p>This document was generated on
-          <b>2008-07-18T14:11:31+09:00</b>.</p></div></div>
+          <b>2008-07-18T14:50:00+09:00</b>.</p></div></div>
     <div id="status">
       <h2>Status of this Document</h2>
     <p><em>
@@ -198,6 +198,8 @@
 </li>
 <li id="comms_wd2-toc"><a href="#comms_wd2">Section 7, Communication</a>
 <ul>
+<li id="event1_wd2-toc"><a href="#event1_wd2">Section 7.1, Event definitions</a>
+</li>
 <li id="server-sent-events_wd2-toc"><a href="#server-sent-events_wd2">Section 7.2, Server-sent DOM events</a>
 </li>
 <li id="network_wd2-toc"><a href="#network_wd2">Section 7.3, Web sockets [formerly “Network connections”]</a>
@@ -1834,19 +1836,19 @@
             <code>Window</code> object. In this section, the
             following changes were made:</p>
             <ul>
-              <li>In the “APIs for creating and navigating browsing
-              contexts by name” subsection, an
-              instance of the
-              phrase “browsing context corresponding to the Window
-              object that is the script execution context” was
-              changed to <q>script browsing context</q>.</li>
-              <li>A statement concerning the
-              <code>AbstractView</code> object was updated to now
-              read (added text highlighted): <q>The AbstractView
-                object of default views must also implement the
-                Window, <em class="highlight">WindowBrowsingContext, and EventTarget</em>
-                interfaces.</q></li>
-              <li>A interface definition for the 
+              <li>The following pair of statements were added:
+              <blockquote>
+                <p><q>Each Document in a browsing context also has
+                  an associated list of message ports, which must
+                  be initially empty. The list is used during
+                  history traversal in much the same way as the
+                  list of added properties, to keep track of
+                  message ports that need to be reactivated if the
+                  Document is made the active document
+                  again.</q></p>
+              </blockquote>
+              </li>
+              <li>An interface definition for the 
               <code>WindowBrowsingContext</code> interface
               was
               added (this addition effectively splits the previous
@@ -1884,6 +1886,18 @@
               by scripts whose effective script origin is not the
               same as the Window object’s browsing context’s
               active document’s effective script origin.</li>
+              <li>In the “APIs for creating and navigating browsing
+              contexts by name” subsection, an
+              instance of the
+              phrase “browsing context corresponding to the Window
+              object that is the script execution context” was
+              changed to <q>script browsing context</q>.</li>
+              <li>A statement concerning the
+              <code>AbstractView</code> object was updated to now
+              read (added text highlighted): <q>The AbstractView
+                object of default views must also implement the
+                Window, <em class="highlight">WindowBrowsingContext, and EventTarget</em>
+                interfaces.</q></li>
             </ul>
           </div>
           <div id="origin_wd2" class="section">
@@ -2161,6 +2175,27 @@
               algorithm which specifies user-agent behavior when a
               browsing context is navigated to a new
               resource.</li>
+              <li>In the “History traversal” subsection, the
+              following statements were added as steps in the
+              history-traversal algorithm:
+              <blockquote>
+                <p><q>If there are any
+                MessagePort objects whose owner is the browsing
+                context’s default view’s Window object and that
+                are entangled with another port, the user agent
+                must deactivate all such ports and let the
+                Document’s list of message ports be a list of
+                those ports.</q></p>
+                <p>…</p>
+                <p><q>If the active document’s list of message
+                  ports is not empty, then the user agent must
+                  reactivate all the ports in that list. Empty
+                  that list of message ports.</q></p>
+              </blockquote>
+              </li>
+              <li>A new “Closing a browsing context” subsection
+              was added. It is currently a placeholder, with
+              editorial notes about its intended purpose.</li>
             </ul>
           </div>
           <div id="structured_wd2" class="section">
@@ -2251,16 +2286,38 @@
           <p>Applications written in HTML often require mechanisms
           to communicate with remote servers, as well mechanisms
           for applications from different domains running on the
-          same client to communicate with each other (so-called
-          “cross-document messaging”). This section defines APIs for
+          same client to communicate with each other. This section
+          defines APIs for
           enabling those classes of communication; specifically,
           APIs for cross-document messaging, for server-sent DOM
-          events, and for so-called “Web Sockets” (for enabling
+          events, for “Web Sockets” (for enabling
           Web applications to maintain bidirectional
-          communications with their originating server) — as well
-          as providing the interface definitions for messages sent
-          in cross-document messaging and server-sent DOM
-          events.</p>
+          communications with their originating server),
+          and for “channel messaging”.</p>
+          <div id="event1_wd2" class="section">
+            <h2>Section 7.1, Event definitions <a class="hash" href="#event1_wd2">#</a> <a class="toc-bak" href="#event1_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#event1">Section 7.1, Event definitions</a>” in the
+        current “Editor’s Draft”
+        version of the specification.</p><p class="spec-link">View
+        
+        “<a href="http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html#event1">Section 7.1, Event definitions</a>”
+        in a
+        diff-marked version of the specification, showing
+        changes made between
+        10 June 2008
+        and 
+        current “Editor’s Draft”.</p></div>
+            <p>This section defines the <code>MessageEvent</code>
+            interface. In this section, the following changes were
+            made:</p>
+            <ul>
+              <li>The
+              <code class="domattribute">messagePort</code>
+              attribute
+              was added to the interface definition for the
+              <code>MessageEvent</code>
+              interface.</li>
+            </ul>
+          </div>
           <div id="server-sent-events_wd2" class="section">
             <h2>Section 7.2, Server-sent DOM events <a class="hash" href="#server-sent-events_wd2">#</a> <a class="toc-bak" href="#server-sent-events_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#server-sent-events">Section 7.2, Server-sent DOM events</a>” in the
         current “Editor’s Draft”

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.308
retrieving revision 1.309
diff -u -d -r1.308 -r1.309
--- Overview.src.html	18 Jul 2008 05:12:07 -0000	1.308
+++ Overview.src.html	18 Jul 2008 05:51:25 -0000	1.309
@@ -988,20 +988,19 @@
             <code>Window</code> object. In this section, the
             following changes were made:</p>
             <ul>
-              <li>In the “APIs for creating and navigating browsing
-              contexts by name” subsection, an
-              instance of the
-              phrase “browsing context corresponding to the Window
-              object that is the script execution context” was
-              changed to <q>script browsing context</q>.</li>
-              <li>A statement concerning the
-              <code>AbstractView</code> object was updated to now
-              read (added text highlighted): <q>The AbstractView
-                object of default views must also implement the
-                Window, <em class=highlight
-                  >WindowBrowsingContext, and EventTarget</em>
-                interfaces.</q></li>
-              <li>A interface definition for the 
+              <li>The following pair of statements were added:
+              <blockquote>
+                <p><q>Each Document in a browsing context also has
+                  an associated list of message ports, which must
+                  be initially empty. The list is used during
+                  history traversal in much the same way as the
+                  list of added properties, to keep track of
+                  message ports that need to be reactivated if the
+                  Document is made the active document
+                  again.</q></p>
+              </blockquote>
+              </li>
+              <li>An interface definition for the 
               <code>WindowBrowsingContext</code> interface
               was
               added (this addition effectively splits the previous
@@ -1041,6 +1040,19 @@
               by scripts whose effective script origin is not the
               same as the Window object’s browsing context’s
               active document’s effective script origin.</li>
+              <li>In the “APIs for creating and navigating browsing
+              contexts by name” subsection, an
+              instance of the
+              phrase “browsing context corresponding to the Window
+              object that is the script execution context” was
+              changed to <q>script browsing context</q>.</li>
+              <li>A statement concerning the
+              <code>AbstractView</code> object was updated to now
+              read (added text highlighted): <q>The AbstractView
+                object of default views must also implement the
+                Window, <em class=highlight
+                  >WindowBrowsingContext, and EventTarget</em>
+                interfaces.</q></li>
             </ul>
           </section>
           <section id=origin_wd2>
@@ -1260,6 +1272,27 @@
               algorithm which specifies user-agent behavior when a
               browsing context is navigated to a new
               resource.</li>
+              <li>In the “History traversal” subsection, the
+              following statements were added as steps in the
+              history-traversal algorithm:
+              <blockquote>
+                <p><q>If there are any
+                MessagePort objects whose owner is the browsing
+                context’s default view’s Window object and that
+                are entangled with another port, the user agent
+                must deactivate all such ports and let the
+                Document’s list of message ports be a list of
+                those ports.</q></p>
+                <p>…</p>
+                <p><q>If the active document’s list of message
+                  ports is not empty, then the user agent must
+                  reactivate all the ports in that list. Empty
+                  that list of message ports.</q></p>
+              </blockquote>
+              </li>
+              <li>A new “Closing a browsing context” subsection
+              was added. It is currently a placeholder, with
+              editorial notes about its intended purpose.</li>
             </ul>
           </section>
           <section id=structured_wd2>
@@ -1311,16 +1344,28 @@
           <p>Applications written in HTML often require mechanisms
           to communicate with remote servers, as well mechanisms
           for applications from different domains running on the
-          same client to communicate with each other (so-called
-          “cross-document messaging”). This section defines APIs for
+          same client to communicate with each other. This section
+          defines APIs for
           enabling those classes of communication; specifically,
           APIs for cross-document messaging, for server-sent DOM
-          events, and for so-called “Web Sockets” (for enabling
+          events, for “Web Sockets” (for enabling
           Web applications to maintain bidirectional
-          communications with their originating server) — as well
-          as providing the interface definitions for messages sent
-          in cross-document messaging and server-sent DOM
-          events.</p>
+          communications with their originating server),
+          and for “channel messaging”.</p>
+          <section id=event1_wd2>
+            <h2>Section 7.1, Event definitions</h2>
+            <p>This section defines the <code>MessageEvent</code>
+            interface. In this section, the following changes were
+            made:</p>
+            <ul>
+              <li>The
+              <code class=domattribute>messagePort</code>
+              attribute
+              was added to the interface definition for the
+              <code>MessageEvent</code>
+              interface.</li>
+            </ul>
+          </section>
           <section id=server-sent-events_wd2>
             <h2>Section 7.2, Server-sent DOM events</h2>
             <p>This section describes a mechanism for allowing
Received on Friday, 18 July 2008 05:52:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:58 GMT