Skip to content

Commit

Permalink
[] (0) Make sure the history is updated before scripts run.
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@4110 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 12, 2009
1 parent cff582a commit 2b6a40f
Show file tree
Hide file tree
Showing 3 changed files with 18 additions and 12 deletions.
10 changes: 6 additions & 4 deletions complete.html
Expand Up @@ -55485,9 +55485,10 @@ <h4 id=read-html><span class=secno>6.11.2 </span><dfn title=navigate-html>Page l
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
Expand Down Expand Up @@ -55544,7 +55545,8 @@ <h4 id=read-xml><span class=secno>6.11.3 </span><dfn title=navigate-xml>Page loa
<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
Expand Down
10 changes: 6 additions & 4 deletions index
Expand Up @@ -52651,9 +52651,10 @@ NETWORK:
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
Expand Down Expand Up @@ -52710,7 +52711,8 @@ NETWORK:
<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
Expand Down
10 changes: 6 additions & 4 deletions source
Expand Up @@ -62667,9 +62667,10 @@ NETWORK:
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
Expand Down Expand Up @@ -62737,7 +62738,8 @@ NETWORK:
<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
Expand Down

0 comments on commit 2b6a40f

Please sign in to comment.