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

html5/pubnotes Overview.html,1.315,1.316 Overview.src.html,1.307,1.308

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 18 Jul 2008 05:12:09 +0000
To: public-html-commits@w3.org
Message-Id: <E1KJiGH-0007mU-GX@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html Overview.src.html 
Log Message:
1.1063 Define the three-argument form of postMessage(). (whatwg r1874)


Index: Overview.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.315
retrieving revision 1.316
diff -u -d -r1.315 -r1.316
--- Overview.html	18 Jul 2008 03:21:43 -0000	1.315
+++ Overview.html	18 Jul 2008 05:12:06 -0000	1.316
@@ -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-18T12:19:02+09:00</b>.</p></div></div>
+          <b>2008-07-18T14:11:31+09:00</b>.</p></div></div>
     <div id="status">
       <h2>Status of this Document</h2>
     <p><em>
@@ -202,7 +202,19 @@
 </li>
 <li id="network_wd2-toc"><a href="#network_wd2">Section 7.3, Web sockets [formerly “Network connections”]</a>
 </li>
-<li id="network_wd2-toc"><a href="#network_wd2">Section 7.5 [NEW], Channel messaging</a>
+<li id="crossDocumentMessages_wd2-toc"><a href="#crossDocumentMessages_wd2">Section 7.4, Cross-document messaging</a>
+<ul>
+<li id="introduction5_wd2-toc"><a href="#introduction5_wd2">Section 7.4.1, Introduction</a>
+</li>
+<li id="security9_wd2-toc"><a href="#security9_wd2">Section 7.4.2, Security</a>
+</li>
+<li id="posting_wd2-toc"><a href="#posting_wd2">Section 7.4.3, Posting text</a>
+</li>
+<li id="posting0_wd2-toc"><a href="#posting0_wd2">Section 7.4.4, Posting message ports</a>
+</li>
+</ul>
+</li>
+<li id="channel0_wd2-toc"><a href="#channel0_wd2">Section 7.5 [NEW], Channel messaging</a>
 </li>
 </ul>
 </li>
@@ -1835,12 +1847,43 @@
                 Window, <em class="highlight">WindowBrowsingContext, and EventTarget</em>
                 interfaces.</q></li>
               <li>A interface definition for the 
-              <code>WindowBrowsingContext</code> interface was
+              <code>WindowBrowsingContext</code> interface
+              was
               added (this addition effectively splits the previous
               definition for the <code>Window</code> interface
               into two parts: one for the <code>Window</code>
               interface, and one for the
               <code>WindowBrowsingContext</code> interface.</li>
+              <li>The
+                <code class="method">postMessage(<var>message</var>,
+                <var>messagePort</var>,
+                <var>targetOrigin</var>)</code> form (“three
+              argument” form) of the
+              <code class="method">postMessage()</code>
+              method
+              was added to the interface definition for
+              the 
+              <code>WindowBrowsingContext</code> interface.</li>
+              <li>In the “Security” subsection, 
+              text was refined to make it clear that both
+              the 
+              <code class="method">postMessage(<var>message</var>,
+                <var>targetOrigin</var>)</code> form (“two argument”
+              form)
+              and
+                <code class="method">postMessage(<var>message</var>,
+                <var>messagePort</var>,
+                <var>targetOrigin</var>)</code> form (“three
+              argument” form) of the
+              <code class="method">postMessage()</code>
+              method
+              are in the set of
+              members of a <code>Window</code> object for which it
+              is not a requirement that a security
+              exception be raised when they are accessed
+              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>
             </ul>
           </div>
           <div id="origin_wd2" class="section">
@@ -2295,12 +2338,104 @@
               Web-socket-enabled server communicate</li>
             </ul>
           </div>
-          <div id="network_wd2" class="section">
-            <h2>Section 7.5 [NEW], Channel messaging <a class="hash" href="#network_wd2">#</a> <a class="toc-bak" href="#network_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#network">Section 7.5 [NEW], Channel messaging</a>” in the
+          <div id="crossDocumentMessages_wd2" class="section">
+            <h2>Section 7.4, Cross-document messaging <a class="hash" href="#crossDocumentMessages_wd2">#</a> <a class="toc-bak" href="#crossDocumentMessages_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#crossDocumentMessages">Section 7.4, Cross-document messaging</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#network">Section 7.5 [NEW], Channel messaging</a>”
+        “<a href="http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html#crossDocumentMessages">Section 7.4, Cross-document messaging</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 introduces a messaging system, using the
+            <code class="method">postMessage()</code> method, that
+            allows documents to communicate with each other
+            regardless of their source domain, in a way designed to
+            not enable cross-site scripting attacks.</p>
+            <div id="introduction5_wd2" class="section">
+              <h2>Section 7.4.1, Introduction <a class="hash" href="#introduction5_wd2">#</a> <a class="toc-bak" href="#introduction5_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#introduction5">Section 7.4.1, Introduction</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#introduction5">Section 7.4.1, Introduction</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 newly titled subsection was formed from
+              examples and their accompanying explanatory text
+              from what had been the “Processing model” subsection
+              in previous drafts.</p>
+            </div>
+            <div id="security9_wd2" class="section">
+              <h2>Section 7.4.2, Security <a class="hash" href="#security9_wd2">#</a> <a class="toc-bak" href="#security9_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#security9">Section 7.4.2, Security</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#security9">Section 7.4.2, Security</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 newly titled subsection was formed from a
+              number of warnings that had been in the “Processing
+              model” subsection in previous drafts.</p>
+            </div>
+            <div id="posting_wd2" class="section">
+              <h2>Section 7.4.3, Posting text <a class="hash" href="#posting_wd2">#</a> <a class="toc-bak" href="#posting_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#posting">Section 7.4.3, Posting text</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#posting">Section 7.4.3, Posting text</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 newly titled subsection was formed from what
+              the what had been the core content “Processing
+              model” subsection in previous drafts — that is,
+              text specifying user-agent behavior for the
+              <code class="method">postMessage(<var>message</var>,
+                <var>targetOrigin</var>)</code> form (“two argument”
+              form) of the
+              <code class="method">postMessage()</code>
+              method.</p>
+            </div>
+            <div id="posting0_wd2" class="section">
+              <h2>Section 7.4.4, Posting message ports <a class="hash" href="#posting0_wd2">#</a> <a class="toc-bak" href="#posting0_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#posting0">Section 7.4.4, Posting message ports</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#posting0">Section 7.4.4, Posting message ports</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 newly added subsection specifies user-agent
+              behavior for the <code class="method">postMessage(<var>message</var>,
+                <var>messagePort</var>,
+                <var>targetOrigin</var>)</code> form (“three
+              argument” form) of the <code class="method">postMessage()</code>
+              method.</p>
+            </div>
+          </div>
+          <div id="channel0_wd2" class="section">
+            <h2>Section 7.5 [NEW], Channel messaging <a class="hash" href="#channel0_wd2">#</a> <a class="toc-bak" href="#channel0_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#channel0">Section 7.5 [NEW], Channel messaging</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#channel0">Section 7.5 [NEW], Channel messaging</a>”
         in a
         diff-marked version of the specification, showing
         changes made between

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.307
retrieving revision 1.308
diff -u -d -r1.307 -r1.308
--- Overview.src.html	18 Jul 2008 03:21:43 -0000	1.307
+++ Overview.src.html	18 Jul 2008 05:12:07 -0000	1.308
@@ -1002,12 +1002,45 @@
                   >WindowBrowsingContext, and EventTarget</em>
                 interfaces.</q></li>
               <li>A interface definition for the 
-              <code>WindowBrowsingContext</code> interface was
+              <code>WindowBrowsingContext</code> interface
+              was
               added (this addition effectively splits the previous
               definition for the <code>Window</code> interface
               into two parts: one for the <code>Window</code>
               interface, and one for the
               <code>WindowBrowsingContext</code> interface.</li>
+              <li>The
+                <code
+                class=method>postMessage(<var>message</var>,
+                <var>messagePort</var>,
+                <var>targetOrigin</var>)</code> form (“three
+              argument” form) of the
+              <code class=method>postMessage()</code>
+              method
+              was added to the interface definition for
+              the 
+              <code>WindowBrowsingContext</code> interface.</li>
+              <li>In the “Security” subsection, 
+              text was refined to make it clear that both
+              the 
+              <code class=method>postMessage(<var>message</var>,
+                <var>targetOrigin</var>)</code> form (“two argument”
+              form)
+              and
+                <code
+                class=method>postMessage(<var>message</var>,
+                <var>messagePort</var>,
+                <var>targetOrigin</var>)</code> form (“three
+              argument” form) of the
+              <code class=method>postMessage()</code>
+              method
+              are in the set of
+              members of a <code>Window</code> object for which it
+              is not a requirement that a security
+              exception be raised when they are accessed
+              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>
             </ul>
           </section>
           <section id=origin_wd2>
@@ -1345,7 +1378,51 @@
               Web-socket-enabled server communicate</li>
             </ul>
           </section>
-          <section id=network_wd2>
+          <section id=crossDocumentMessages_wd2>
+            <h2>Section 7.4, Cross-document messaging</h2>
+            <p>This section introduces a messaging system, using the
+            <code class=method>postMessage()</code> method, that
+            allows documents to communicate with each other
+            regardless of their source domain, in a way designed to
+            not enable cross-site scripting attacks.</p>
+            <section id=introduction5_wd2>
+              <h2>Section 7.4.1, Introduction</h2>
+              <p>This newly titled subsection was formed from
+              examples and their accompanying explanatory text
+              from what had been the “Processing model” subsection
+              in previous drafts.</p>
+            </section>
+            <section id=security9_wd2>
+              <h2>Section 7.4.2, Security</h2>
+              <p>This newly titled subsection was formed from a
+              number of warnings that had been in the “Processing
+              model” subsection in previous drafts.</p>
+            </section>
+            <section id=posting_wd2>
+              <h2>Section 7.4.3, Posting text</h2>
+              <p>This newly titled subsection was formed from what
+              the what had been the core content “Processing
+              model” subsection in previous drafts — that is,
+              text specifying user-agent behavior for the
+              <code class=method>postMessage(<var>message</var>,
+                <var>targetOrigin</var>)</code> form (“two argument”
+              form) of the
+              <code class=method>postMessage()</code>
+              method.</p>
+            </section>
+            <section id=posting0_wd2>
+              <h2>Section 7.4.4, Posting message ports</h2>
+              <p>This newly added subsection specifies user-agent
+              behavior for the <code
+                class=method>postMessage(<var>message</var>,
+                <var>messagePort</var>,
+                <var>targetOrigin</var>)</code> form (“three
+              argument” form) of the <code
+                class=method>postMessage()</code>
+              method.</p>
+            </section>
+          </section>
+          <section id=channel0_wd2>
             <h2>Section 7.5 [NEW], Channel messaging</h2>
             <p>This newly added section defines the
             <code>MessageChannel</code>
Received on Friday, 18 July 2008 05:12:43 GMT

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