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

html5/pubnotes Overview.html,1.283,1.284 Overview.src.html,1.268,1.269

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 01 Jul 2008 23:16:55 +0000
To: public-html-commits@w3.org
Message-Id: <E1KDp5j-0003IX-LZ@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html Overview.src.html 
Log Message:
1.981 "'script document context' and 'script browsing context'


Index: Overview.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.html,v
retrieving revision 1.283
retrieving revision 1.284
diff -u -d -r1.283 -r1.284
--- Overview.html	1 Jul 2008 14:10:48 -0000	1.283
+++ Overview.html	1 Jul 2008 23:16:53 -0000	1.284
@@ -166,6 +166,14 @@
 </li>
 <li id="web-browsers_wd2-toc"><a href="#web-browsers_wd2">Section 5, Web browsers</a>
 <ul>
+<li id="the-default0_wd2-toc"><a href="#the-default0_wd2">Section 5.2, The default view</a>
+</li>
+<li id="origin_wd2-toc"><a href="#origin_wd2">Section 5.3, Origin</a>
+</li>
+<li id="scripting_wd2-toc"><a href="#scripting_wd2">Section 5.4, Scripting</a>
+</li>
+<li id="user-prompts_wd2-toc"><a href="#user-prompts_wd2">Section 5.5, User prompts</a>
+</li>
 <li id="browser_wd2-toc"><a href="#browser_wd2">Section 5.6, Browser state</a>
 </li>
 <li id="history_wd2-toc"><a href="#history_wd2">Section 5.8, Session history and navigation</a>
@@ -1324,7 +1332,13 @@
               <ul>
                 <li>Instances of the phrase “script that will
                 execute as soon as the parser resumes” were
-                changed to <q> pending external script</q>.</li>
+                changed to <q>pending external script</q>.</li>
+                <li>A section of an algorithm that concerns the
+                case when the loading of a script was successful,
+                the following statement was added: <q>The script
+                  document context of the script must be the
+                  Document object that owns the script
+                  element.</q></li>
               </ul>
             </div>
             <div id="the-event-source_wd2" class="section">
@@ -1371,6 +1385,151 @@
           browsers, defines features affecting environments that
           deal with multiple pages, links between pages, and running
           scripts.</p>
+          <div id="the-default0_wd2" class="section">
+            <h2>Section 5.2, The default view <a class="hash" href="#the-default0_wd2">#</a> <a class="toc-bak" href="#the-default0_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#the-default0">Section 5.2, The default view</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#the-default0">Section 5.2, The default view</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 interface for the
+            <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>
+            </ul>
+          </div>
+          <div id="origin_wd2" class="section">
+            <h2>Section 5.3, Origin <a class="hash" href="#origin_wd2">#</a> <a class="toc-bak" href="#origin_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#origin">Section 5.3, Origin</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#origin">Section 5.3, Origin</a>”
+        in a
+        diff-marked version of the specification, showing
+        changes made between
+        10 June 2008
+        and 
+        current “Editor’s Draft”.</p></div>
+            <p>In this section, the following changes were
+            made:</p>
+            <ul>
+              <li>In the algorithm for identifying the
+              <q>owner</q> (by which, in turn, the origin and
+              effective script origin are determined), the
+              following case was added: <q>If a script is in an
+                event handler content attribute: The owner is the
+                Document to which the attribute node
+                belongs.</q></li>
+            </ul>
+          </div>
+          <div id="scripting_wd2" class="section">
+            <h2>Section 5.4, Scripting <a class="hash" href="#scripting_wd2">#</a> <a class="toc-bak" href="#scripting_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#scripting">Section 5.4, Scripting</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#scripting">Section 5.4, Scripting</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 provides conformance criteria
+            related to mechanisms that can cause author-provided
+            executable code to run in the context of a document
+            scripting, as well as defining the states
+            <strong>scripting is enabled</strong> and
+            <strong>scripting is disabled</strong>.</p>
+            <ul>
+              <li>The following statement was added: <q>When a
+                script is created, it is associated with a script
+                execution context, a script browsing context, and
+                a script document context.</q></li>
+              <li>In the “Script execution contexts” subsection, a
+              statement defining the <q>script execution
+                context</q> was updated to read (added text
+              highlighted): <q>The script execution context of a
+                script is defined when that script is created. It
+                is typically <em class="highlight">either</em> a
+                Window object <em class="highlight">or an empty
+                  object</em></q>.</li>
+              <li>Also in the “Script execution contexts”
+              subsection, the following statement was added:
+              <q>When the script execution context of a script is
+                an empty object, it can’t do anything that
+                interacts with the environment.</q></li>
+              <li>Also in the “Script execution contexts”
+              subsection, a related statement was updated to now
+              read (added text highlighted): <q>A script execution
+                context always has an associated browsing
+                context<em class="highlight">, known as the script
+                  browsing context</em>.</q></li>
+              <li>Also in the “Script execution contexts”
+              subsection, the following statement was added:
+              <q>Every script whose script execution context is a
+                Window object is also associated with a Document
+                object, known as its <em class="highlight">script
+                  document context</em>. It is used to resolve
+                URLs. The document is assigned when the script is
+                created, as with the script browsing
+                context.</q></li>
+              <li>In the “The javascript: protocol” subsection, a
+              statement related to navigating the browsing context
+              to a <code>javascript:</code> protocol URL was
+              updated to read (added text highlighted): <q>When a
+                browsing context is navigated to a javascript:
+                URL, and the active document of that browsing
+                context has the same origin as the script given by
+                that URL, the script execution context must be the
+                Window object of the browsing context being
+                navigated<em class="highlight">, and the script
+                  document context must be that active
+                  document</em>.</q></li>
+              <li>In the “Event handler attributes” subsection, a
+              paragraph was updated to read (added text
+              highlighted): <q>The script execution context of the
+                event handler must be the Window object at the end
+                of the scope chain. <em class="highlight">The script
+                  document context of the event handler must be
+                  the Document object that owns the event handler
+                  content attribute that was set</em>.</q></li>
+            </ul>
+          </div>
+          <div id="user-prompts_wd2" class="section">
+            <h2>Section 5.5, User prompts <a class="hash" href="#user-prompts_wd2">#</a> <a class="toc-bak" href="#user-prompts_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#user-prompts">Section 5.5, User prompts</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#user-prompts">Section 5.5, User prompts</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 provides conformance criteria
+            related to dialogs presented to users. In this section,
+            the following changes were made:</p>
+            <ul>
+              <li>In the “Dialogs implemented using separate
+              documents” subsection, in a step in the algorithm
+              that user agents must run when the <code class="method">showModalDialog()</code> method, the
+              phrase “browsing context of the Window object that
+              is the script execution context” was replaced with
+              the phrase <q>script browsing context</q>.</li>
+            </ul>
+          </div>
           <div id="browser_wd2" class="section">
             <h2>Section 5.6, Browser state <a class="hash" href="#browser_wd2">#</a> <a class="toc-bak" href="#browser_wd2-toc">T</a></h2><div class="spec-links"><p class="spec-link">View “<a href="http://www.w3.org/html/wg/html5/#browser">Section 5.6, Browser state</a>” in the
         current “Editor’s Draft”
@@ -1426,6 +1585,11 @@
               <code class="method">pushState()</code>
               method
               is invoked.</li>
+              <li>In the “The Location interface” subsection, an
+              instance of the phrase
+              “browsing context of the Window object that is the
+              script execution context” was changed to <q>script
+                browsing context</q>.</li>
             </ul>
           </div>
           <div id="browsing0_wd2" class="section">

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/pubnotes/Overview.src.html,v
retrieving revision 1.268
retrieving revision 1.269
diff -u -d -r1.268 -r1.269
--- Overview.src.html	1 Jul 2008 14:10:48 -0000	1.268
+++ Overview.src.html	1 Jul 2008 23:16:53 -0000	1.269
@@ -611,7 +611,13 @@
               <ul>
                 <li>Instances of the phrase “script that will
                 execute as soon as the parser resumes” were
-                changed to <q> pending external script</q>.</li>
+                changed to <q>pending external script</q>.</li>
+                <li>A section of an algorithm that concerns the
+                case when the loading of a script was successful,
+                the following statement was added: <q>The script
+                  document context of the script must be the
+                  Document object that owns the script
+                  element.</q></li>
               </ul>
             </section>
             <section id=the-event-source_wd2>
@@ -639,6 +645,112 @@
           browsers, defines features affecting environments that
           deal with multiple pages, links between pages, and running
           scripts.</p>
+          <section id=the-default0_wd2>
+            <h2>Section 5.2, The default view</h2>
+            <p>This section defines the interface for the
+            <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>
+            </ul>
+          </section>
+          <section id=origin_wd2>
+            <h2>Section 5.3, Origin</h2>
+            <p>In this section, the following changes were
+            made:</p>
+            <ul>
+              <li>In the algorithm for identifying the
+              <q>owner</q> (by which, in turn, the origin and
+              effective script origin are determined), the
+              following case was added: <q>If a script is in an
+                event handler content attribute: The owner is the
+                Document to which the attribute node
+                belongs.</q></li>
+            </ul>
+          </section>
+          <section id=scripting_wd2>
+            <h2>Section 5.4, Scripting</h2>
+            <p>This section provides conformance criteria
+            related to mechanisms that can cause author-provided
+            executable code to run in the context of a document
+            scripting, as well as defining the states
+            <strong>scripting is enabled</strong> and
+            <strong>scripting is disabled</strong>.</p>
+            <ul>
+              <li>The following statement was added: <q>When a
+                script is created, it is associated with a script
+                execution context, a script browsing context, and
+                a script document context.</q></li>
+              <li>In the “Script execution contexts” subsection, a
+              statement defining the <q>script execution
+                context</q> was updated to read (added text
+              highlighted): <q>The script execution context of a
+                script is defined when that script is created. It
+                is typically <em class=highlight>either</em> a
+                Window object <em class=highlight>or an empty
+                  object</em></q>.</li>
+              <li>Also in the “Script execution contexts”
+              subsection, the following statement was added:
+              <q>When the script execution context of a script is
+                an empty object, it can’t do anything that
+                interacts with the environment.</q></li>
+              <li>Also in the “Script execution contexts”
+              subsection, a related statement was updated to now
+              read (added text highlighted): <q>A script execution
+                context always has an associated browsing
+                context<em class=highlight>, known as the script
+                  browsing context</em>.</q></li>
+              <li>Also in the “Script execution contexts”
+              subsection, the following statement was added:
+              <q>Every script whose script execution context is a
+                Window object is also associated with a Document
+                object, known as its <em class=highlight>script
+                  document context</em>. It is used to resolve
+                URLs. The document is assigned when the script is
+                created, as with the script browsing
+                context.</q></li>
+              <li>In the “The javascript: protocol” subsection, a
+              statement related to navigating the browsing context
+              to a <code>javascript:</code> protocol URL was
+              updated to read (added text highlighted): <q>When a
+                browsing context is navigated to a javascript:
+                URL, and the active document of that browsing
+                context has the same origin as the script given by
+                that URL, the script execution context must be the
+                Window object of the browsing context being
+                navigated<em class=highlight>, and the script
+                  document context must be that active
+                  document</em>.</q></li>
+              <li>In the “Event handler attributes” subsection, a
+              paragraph was updated to read (added text
+              highlighted): <q>The script execution context of the
+                event handler must be the Window object at the end
+                of the scope chain. <em class=highlight>The script
+                  document context of the event handler must be
+                  the Document object that owns the event handler
+                  content attribute that was set</em>.</q></li>
+            </ul>
+          </section>
+          <section id=user-prompts_wd2>
+            <h2>Section 5.5, User prompts</h2>
+            <p>This section provides conformance criteria
+            related to dialogs presented to users. In this section,
+            the following changes were made:</p>
+            <ul>
+              <li>In the “Dialogs implemented using separate
+              documents” subsection, in a step in the algorithm
+              that user agents must run when the <code
+                class=method>showModalDialog()</code> method, the
+              phrase “browsing context of the Window object that
+              is the script execution context” was replaced with
+              the phrase <q>script browsing context</q>.</li>
+            </ul>
+          </section>
           <section id=browser_wd2>
             <h2>Section 5.6, Browser state</h2>
             <p>This section defines how Web sites can register
@@ -674,6 +786,11 @@
               <code class=method>pushState()</code>
               method
               is invoked.</li>
+              <li>In the “The Location interface” subsection, an
+              instance of the phrase
+              “browsing context of the Window object that is the
+              script execution context” was changed to <q>script
+                browsing context</q>.</li>
             </ul>
           </section>
           <section id=browsing0_wd2>
Received on Tuesday, 1 July 2008 23:17:29 GMT

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