hixie: clarify that history traversal happens in cases other than going back/forward (whatwg r5346)

hixie: clarify that history traversal happens in cases other than going
back/forward (whatwg r5346)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4262&r2=1.4263&f=h
http://html5.org/tools/web-apps-tracker?from=5345&to=5346

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4262
retrieving revision 1.4263
diff -u -d -r1.4262 -r1.4263
--- Overview.html 25 Aug 2010 00:13:47 -0000 1.4262
+++ Overview.html 25 Aug 2010 00:15:39 -0000 1.4263
@@ -43942,7 +43942,14 @@
 
   <p>When a user agent is required to <dfn id="traverse-the-history">traverse the history</dfn>
   to a <i>specified entry</i>, optionally with <a href="#replacement-enabled">replacement
-  enabled</a>, the user agent must act as follows:</p>
+  enabled</a>, the user agent must act as follows.</p>
+
+  <p class="note">This algorithm is not just invoked when <a href="#traverse-the-history-by-a-delta" title="traverse the history by a delta">explicitly going back or
+  forwards in the session history</a> &mdash; it is also invoked in
+  other situations, for example when <a href="#navigate" title="navigate">navigating
+  a browsing context</a>, as part of <a href="#update-the-session-history-with-the-new-page" title="update the session
+  history with the new page">updating the session history with the new
+  page</a>.</p>
 
   <ol><li><p>If there is no longer a <code><a href="#document">Document</a></code> object for the
    entry in question, the user agent must <a href="#navigate">navigate</a> the

Received on Wednesday, 25 August 2010 00:16:23 UTC