[html5] r4110 - [] (0) Make sure the history is updated before scripts run.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-11 22:55:24 -0700 (Sun, 11 Oct 2009)
New Revision: 4110

Modified:
   complete.html
   index
   source
Log:
[] (0) Make sure the history is updated before scripts run.

Modified: complete.html
===================================================================
--- complete.html	2009-10-12 05:51:04 UTC (rev 4109)
+++ complete.html	2009-10-12 05:55:24 UTC (rev 4110)
@@ -55485,9 +55485,10 @@
   which eventually causes a <code title=event-load>load</code> event
   to be fired.</p>
 
-  <p>After creating the <code>Document</code> object, but potentially
-  before the page has finished parsing, the user agent must
-  <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>
+  <p>After creating the <code>Document</code> object, but before any
+  script execution, certainly before the parser <a href=#stop-parsing title="stop
+  parsing">stops</a>, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session
+  history with the new page</a>.</p>
 
   <p class=note><a href=#concept-appcache-init title=concept-appcache-init>Application
   cache selection</a> happens <a href=#parser-appcache>in the
@@ -55544,7 +55545,8 @@
   <p>Otherwise, then, with the newly created <code>Document</code>,
   the user agents must <a href=#update-the-session-history-with-the-new-page>update the session history with the new
   page</a>. User agents may do this before the complete document
-  has been parsed (thus achieving <i>incremental rendering</i>).</p>
+  has been parsed (thus achieving <i>incremental rendering</i>), and
+  must do this before any scripts are to be executed.</p>
 
   <p>Error messages from the parse process (e.g. XML namespace
   well-formedness errors) may be reported inline by mutating the

Modified: index
===================================================================
--- index	2009-10-12 05:51:04 UTC (rev 4109)
+++ index	2009-10-12 05:55:24 UTC (rev 4110)
@@ -52651,9 +52651,10 @@
   which eventually causes a <code title=event-load>load</code> event
   to be fired.</p>
 
-  <p>After creating the <code>Document</code> object, but potentially
-  before the page has finished parsing, the user agent must
-  <a href=#update-the-session-history-with-the-new-page>update the session history with the new page</a>.</p>
+  <p>After creating the <code>Document</code> object, but before any
+  script execution, certainly before the parser <a href=#stop-parsing title="stop
+  parsing">stops</a>, the user agent must <a href=#update-the-session-history-with-the-new-page>update the session
+  history with the new page</a>.</p>
 
   <p class=note><a href=#concept-appcache-init title=concept-appcache-init>Application
   cache selection</a> happens <a href=#parser-appcache>in the
@@ -52710,7 +52711,8 @@
   <p>Otherwise, then, with the newly created <code>Document</code>,
   the user agents must <a href=#update-the-session-history-with-the-new-page>update the session history with the new
   page</a>. User agents may do this before the complete document
-  has been parsed (thus achieving <i>incremental rendering</i>).</p>
+  has been parsed (thus achieving <i>incremental rendering</i>), and
+  must do this before any scripts are to be executed.</p>
 
   <p>Error messages from the parse process (e.g. XML namespace
   well-formedness errors) may be reported inline by mutating the

Modified: source
===================================================================
--- source	2009-10-12 05:51:04 UTC (rev 4109)
+++ source	2009-10-12 05:55:24 UTC (rev 4110)
@@ -62667,9 +62667,10 @@
   which eventually causes a <code title="event-load">load</code> event
   to be fired.</p>
 
-  <p>After creating the <code>Document</code> object, but potentially
-  before the page has finished parsing, the user agent must
-  <span>update the session history with the new page</span>.</p>
+  <p>After creating the <code>Document</code> object, but before any
+  script execution, certainly before the parser <span title="stop
+  parsing">stops</span>, the user agent must <span>update the session
+  history with the new page</span>.</p>
 
   <p class="note"><span title="concept-appcache-init">Application
   cache selection</span> happens <a href="#parser-appcache">in the
@@ -62737,7 +62738,8 @@
   <p>Otherwise, then, with the newly created <code>Document</code>,
   the user agents must <span>update the session history with the new
   page</span>. User agents may do this before the complete document
-  has been parsed (thus achieving <i>incremental rendering</i>).</p>
+  has been parsed (thus achieving <i>incremental rendering</i>), and
+  must do this before any scripts are to be executed.</p>
 
   <p>Error messages from the parse process (e.g. XML namespace
   well-formedness errors) may be reported inline by mutating the