html5/pubnotes Overview.html,1.313,1.314 Overview.src.html,1.305,1.306

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

Modified Files:
	Overview.html Overview.src.html 
Log Message:
1.1068 Split Window into two (editorial-level) definitions. Clean up some timeout stuff. (whatwg r1879)


Index: Overview.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.313
retrieving revision 1.314
diff -u -d -r1.313 -r1.314
--- Overview.html	16 Jul 2008 06:33:07 -0000	1.313
+++ Overview.html	16 Jul 2008 08:12:04 -0000	1.314
@@ -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-16T15:27:32+09:00</b>.</p></div></div>
+          <b>2008-07-16T17:10:38+09:00</b>.</p></div></div>
     <div id="status">
       <h2>Status of this Document</h2>
     <p><em>
@@ -212,6 +212,9 @@
 </li>
 </ul>
 </li>
+<li id="no_wd2-toc"><a href="#no_wd2">Section 10, Things that you can't do with this
+            specification…</a>
+</li>
 <li id="acknowledgements_wd2-toc"><a href="#acknowledgements_wd2">Acknowledgements</a>
 </li>
 </ul>
@@ -1823,6 +1826,19 @@
               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 
+              <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>
             </ul>
           </div>
           <div id="origin_wd2" class="section">
@@ -1946,7 +1962,7 @@
                     execution context always has an associated
                     browsing context, known as the script browsing
                     context. If the script execution context is a
-                    <em class="highlighted">WindowBrowsingContext</em> object, then
+                    <em class="highlight">WindowBrowsingContext</em> object, then
                     that object’s browsing context is it</q> (the
                   text had previously referred to the
                   <code>Window</code> object).</li>
@@ -2409,6 +2425,34 @@
             </ul>
           </div>
         </div>
+        <div id="no_wd2" class="section">
+          <h2>Section 10, Things that you can't do with this
+            specification… <a class="hash" href="#no_wd2">#</a> <a class="toc-bak" href="#no_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#no">Section 10, Things that you can't do with this
+            specification…</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#no">Section 10, Things that you can't do with this
+            specification…</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 mostly non-normative section describes certain
+          features that the specification, by design, does not
+          address — because “a client-side markup language is not
+          the right level for them, or because the features exist in
+          other languages that can be integrated into” HTML. In this
+          section, the following changes were made:</p>
+          <ul>
+            <li>In the “Timers” subsection, the following
+            statement was added: <q>Objects that implement the
+              Window interface must also implement the
+              WindowTimers interface</q>.</li>
+          </ul>
+        </div>
         <div id="acknowledgements_wd2" class="section">
           <h2>Acknowledgements <a class="hash" href="#acknowledgements_wd2">#</a> <a class="toc-bak" href="#acknowledgements_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#acknowledgements">Acknowledgements</a>” in the
         current “Editor’s Draft”

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.305
retrieving revision 1.306
diff -u -d -r1.305 -r1.306
--- Overview.src.html	16 Jul 2008 06:33:07 -0000	1.305
+++ Overview.src.html	16 Jul 2008 08:12:04 -0000	1.306
@@ -994,6 +994,20 @@
               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 
+              <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>
             </ul>
           </section>
           <section id=origin_wd2>
@@ -1097,7 +1111,7 @@
                     execution context always has an associated
                     browsing context, known as the script browsing
                     context. If the script execution context is a
-                    <em class=highlighted
+                    <em class=highlight
                       >WindowBrowsingContext</em> object, then
                     that object’s browsing context is it</q> (the
                   text had previously referred to the
@@ -1433,6 +1447,22 @@
             </ul>
           </section>
         </section>
+        <section id=no_wd2>
+          <h2>Section 10, Things that you can't do with this
+            specification…</h2>
+          <p>This mostly non-normative section describes certain
+          features that the specification, by design, does not
+          address — because “a client-side markup language is not
+          the right level for them, or because the features exist in
+          other languages that can be integrated into” HTML. In this
+          section, the following changes were made:</p>
+          <ul>
+            <li>In the “Timers” subsection, the following
+            statement was added: <q>Objects that implement the
+              Window interface must also implement the
+              WindowTimers interface</q>.</li>
+          </ul>
+        </section>
         <section id=acknowledgements_wd2>
           <h2>Acknowledgements</h2>
           <p>The following names were added to the list of names in

Received on Wednesday, 16 July 2008 08:12:41 UTC