- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 15 Sep 2009 01:29:36 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv5730
Modified Files:
Overview.html
Log Message:
Make hashchange and popstate fire after scrolling and UA updates. (whatwg r3850)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3016
retrieving revision 1.3017
diff -u -d -r1.3016 -r1.3017
--- Overview.html 15 Sep 2009 01:07:13 -0000 1.3016
+++ Overview.html 15 Sep 2009 01:29:32 -0000 1.3017
@@ -49344,12 +49344,17 @@
created. (This can never happen with <a href="#replacement-enabled">replacement
enabled</a>.)</li>
- <li><p>If appropriate, update the <a href="#current-entry">current entry</a> in the
- <a href="#browsing-context">browsing context</a>'s <code>Document</code> object's
- <code><a href="#history-0">History</a></code> object to reflect any state that the user
- agent wishes to persist.</p>
- <p class="example">For example, some user agents might want to
- persist the scroll position, or the values of form controls.</p>
+ <li>
+
+ <p>If appropriate, update the <a href="#current-entry">current entry</a> in the
+ <a href="#browsing-context">browsing context</a>'s <code>Document</code> object's
+ <code><a href="#history-0">History</a></code> object to reflect any state that the user
+ agent wishes to persist. The entry is then said to be <dfn id="an-entry-with-persisted-user-state">an
+ entry with persisted user state</dfn>.</p>
+
+ <p class="example">For example, some user agents might want to
+ persist the scroll position, or the values of form controls.</p>
+
</li>
<li><p>If the <i>specified entry</i> has a different
@@ -49412,21 +49417,24 @@
<li><p>If the traversal was initiated with <dfn id="replacement-enabled">replacement
enabled</dfn>, remove the entry immediately before the
- <span>specified entry</span> in the session history.</p>
+ <var title="">specified entry</var> in the session history.</p>
+
+ <li><p>If <var title="">hash changed</var> is true, then, if the
+ new URL has a fragment identifier, <a href="#scroll-to-the-fragment-identifier">scroll to the fragment
+ identifier</a>.</li>
+
+ <li><p>If the entry is <a href="#an-entry-with-persisted-user-state">an entry with persisted user
+ state</a>, the user agent may update aspects of the document
+ view, for instance the scroll position or values of form fields,
+ that it had previously recorded.</li>
<li><p>If the <i>specified entry</i> is a state object or the
first entry for a <code>Document</code>, the user agent must <a href="#activating-state-object-entries" title="activate the state object">activate that
entry</a>.</li>
- <li><p>If <var title="">hash changed</var> is true, then first,
+ <li><p>If <var title="">hash changed</var> is true, then
synchronously <a href="#fire-a-simple-event">fire a simple event</a> with the name <code title="event-hashchange">hashchange</code> at the <a href="#browsing-context">browsing
- context</a>'s <code><a href="#window">Window</a></code> object; and second, if the new
- URL has a fragment identifier, <a href="#scroll-to-the-fragment-identifier">scroll to the fragment
- identifier</a>.</li>
-
- <li><p>User agents may also update other aspects of the document
- view when the location changes in this way, for instance the scroll
- position, values of form fields, etc.</li>
+ context</a>'s <code><a href="#window">Window</a></code> object.</li>
<li><p>The <a href="#current-entry">current entry</a> is now the <i>specified
entry</i>.</li>
Received on Tuesday, 15 September 2009 01:29:44 UTC