[html5] r8052 - [e] (0) Try to clarify that this isn't navigating to URLs. Affected topics: HTML

[whatwg at whatwg.org]

Author: ianh
Date: 2013-07-12 12:27:01 -0700 (Fri, 12 Jul 2013)
New Revision: 8052

Modified:
   complete.html
   index
   source
Log:
[e] (0) Try to clarify that this isn't navigating to URLs.
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2013-07-12 18:07:28 UTC (rev 8051)
+++ complete.html	2013-07-12 19:27:01 UTC (rev 8052)
@@ -68692,15 +68692,25 @@
   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,
-   <a href=#navigate>navigate</a><!--DONAV history traversal after eviction--> the browsing context to the
-   location for that entry to perform an <a href=#entry-update>entry update</a> of that entry, and abort these
-   steps. The "<a href=#navigate>navigate</a>" algorithm reinvokes this "traverse" algorithm to complete the
-   traversal, at which point there <em>is</em> a <code><a href=#document>Document</a></code> object and so this step gets
-   skipped. The navigation must be done using the same <a href=#source-browsing-context>source browsing context</a> as was
-   used the first time this entry was created. (This can never happen with <a href=#replacement-enabled>replacement
-   enabled</a>.)</li>
+  <ol><li>
 
+    <p>If there is no longer a <code><a href=#document>Document</a></code> object for the entry in question,
+    <a href=#navigate>navigate</a><!--DONAV history traversal after eviction--> the <a href=#browsing-context>browsing context</a> to the
+    resource for that entry to perform an <a href=#entry-update>entry update</a> of that entry, and abort these
+    steps. The "<a href=#navigate>navigate</a>" algorithm reinvokes this "traverse" algorithm to complete the
+    traversal, at which point there <em>is</em> a <code><a href=#document>Document</a></code> object and so this step gets
+    skipped. The navigation must be done using the same <a href=#source-browsing-context>source browsing context</a> as was
+    used the first time this entry was created. (This can never happen with <a href=#replacement-enabled>replacement
+    enabled</a>.)</p>
+
+    <p class=note>If the resource was obtained usign a non-idempotent action, for example a POST
+    form submission, or if the resource is no longer available, for example because the computer is
+    now offline and the page wasn't cached, navigating to it again might not be possible. In this
+    case, the navigation will result in a different page than previously; for example, it might be
+    an error message explaining the problem or offering to resubmit the form.</p>
+
+   </li>
+
    <li><p>If the <a href=#current-entry>current entry</a>'s title was not set by the <code title=dom-history-pushState><a href=#dom-history-pushstate>pushState()</a></code> or <code title=dom-history-replaceState><a href=#dom-history-replacestate>replaceState()</a></code> methods, then set its title to the value
    returned by the <code title=dom-document-title><a href=#document.title>document.title</a></code> IDL attribute.</li>
 

Modified: index
===================================================================
--- index	2013-07-12 18:07:28 UTC (rev 8051)
+++ index	2013-07-12 19:27:01 UTC (rev 8052)
@@ -68692,15 +68692,25 @@
   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,
-   <a href=#navigate>navigate</a><!--DONAV history traversal after eviction--> the browsing context to the
-   location for that entry to perform an <a href=#entry-update>entry update</a> of that entry, and abort these
-   steps. The "<a href=#navigate>navigate</a>" algorithm reinvokes this "traverse" algorithm to complete the
-   traversal, at which point there <em>is</em> a <code><a href=#document>Document</a></code> object and so this step gets
-   skipped. The navigation must be done using the same <a href=#source-browsing-context>source browsing context</a> as was
-   used the first time this entry was created. (This can never happen with <a href=#replacement-enabled>replacement
-   enabled</a>.)</li>
+  <ol><li>
 
+    <p>If there is no longer a <code><a href=#document>Document</a></code> object for the entry in question,
+    <a href=#navigate>navigate</a><!--DONAV history traversal after eviction--> the <a href=#browsing-context>browsing context</a> to the
+    resource for that entry to perform an <a href=#entry-update>entry update</a> of that entry, and abort these
+    steps. The "<a href=#navigate>navigate</a>" algorithm reinvokes this "traverse" algorithm to complete the
+    traversal, at which point there <em>is</em> a <code><a href=#document>Document</a></code> object and so this step gets
+    skipped. The navigation must be done using the same <a href=#source-browsing-context>source browsing context</a> as was
+    used the first time this entry was created. (This can never happen with <a href=#replacement-enabled>replacement
+    enabled</a>.)</p>
+
+    <p class=note>If the resource was obtained usign a non-idempotent action, for example a POST
+    form submission, or if the resource is no longer available, for example because the computer is
+    now offline and the page wasn't cached, navigating to it again might not be possible. In this
+    case, the navigation will result in a different page than previously; for example, it might be
+    an error message explaining the problem or offering to resubmit the form.</p>
+
+   </li>
+
    <li><p>If the <a href=#current-entry>current entry</a>'s title was not set by the <code title=dom-history-pushState><a href=#dom-history-pushstate>pushState()</a></code> or <code title=dom-history-replaceState><a href=#dom-history-replacestate>replaceState()</a></code> methods, then set its title to the value
    returned by the <code title=dom-document-title><a href=#document.title>document.title</a></code> IDL attribute.</li>
 

Modified: source
===================================================================
--- source	2013-07-12 18:07:28 UTC (rev 8051)
+++ source	2013-07-12 19:27:01 UTC (rev 8052)
@@ -76691,15 +76691,25 @@
 
   <ol>
 
-   <li><p>If there is no longer a <code>Document</code> object for the entry in question,
-   <span>navigate</span><!--DONAV history traversal after eviction--> the browsing context to the
-   location for that entry to perform an <span>entry update</span> of that entry, and abort these
-   steps. The "<span>navigate</span>" algorithm reinvokes this "traverse" algorithm to complete the
-   traversal, at which point there <em>is</em> a <code>Document</code> object and so this step gets
-   skipped. The navigation must be done using the same <span>source browsing context</span> as was
-   used the first time this entry was created. (This can never happen with <span>replacement
-   enabled</span>.)</p></li>
+   <li>
 
+    <p>If there is no longer a <code>Document</code> object for the entry in question,
+    <span>navigate</span><!--DONAV history traversal after eviction--> the <span>browsing context</span> to the
+    resource for that entry to perform an <span>entry update</span> of that entry, and abort these
+    steps. The "<span>navigate</span>" algorithm reinvokes this "traverse" algorithm to complete the
+    traversal, at which point there <em>is</em> a <code>Document</code> object and so this step gets
+    skipped. The navigation must be done using the same <span>source browsing context</span> as was
+    used the first time this entry was created. (This can never happen with <span>replacement
+    enabled</span>.)</p>
+
+    <p class="note">If the resource was obtained usign a non-idempotent action, for example a POST
+    form submission, or if the resource is no longer available, for example because the computer is
+    now offline and the page wasn't cached, navigating to it again might not be possible. In this
+    case, the navigation will result in a different page than previously; for example, it might be
+    an error message explaining the problem or offering to resubmit the form.</p>
+
+   </li>
+
    <li><p>If the <span>current entry</span>'s title was not set by the <code
    title="dom-history-pushState">pushState()</code> or <code
    title="dom-history-replaceState">replaceState()</code> methods, then set its title to the value