[html5] r4594 - [giow] (2) Correct how 'entry update' is to happen to also update the other entr [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jan 14 23:00:14 PST 2010
Author: ianh
Date: 2010-01-14 23:00:11 -0800 (Thu, 14 Jan 2010)
New Revision: 4594
Modified:
complete.html
index
source
Log:
[giow] (2) Correct how 'entry update' is to happen to also update the other entries that referenced the document, and to not blow away state objects.
Modified: complete.html
===================================================================
--- complete.html 2010-01-15 06:37:12 UTC (rev 4593)
+++ complete.html 2010-01-15 07:00:11 UTC (rev 4594)
@@ -56552,16 +56552,17 @@
<dd>
- <ol><li><p>Replace the entry being updated with a new entry
- representing the new resource and its <code>Document</code>
- object and related state. The user agent may propagate state from
- the old entry to the new entry (e.g. scroll position).</li>
+ <ol><li><p>Replace the <code>Document</code> of the entry being
+ updated, and any other entries that referenced the same
+ document as that entry, with the new
+ <code>Document</code>.</li>
<li><p><a href=#traverse-the-history>Traverse the history</a> to the new
entry.</li>
</ol><p class=note>This can only happen if the entry being updated
- is no the <a href=#current-entry>current entry</a>. (It happens when the user
+ is no the <a href=#current-entry>current entry</a>, and can never happen with
+ <a href=#replacement-enabled>replacement enabled</a>. (It happens when the user
tried to traverse to a session history entry that no longer had
a <code>Document</code> object.)</p>
Modified: index
===================================================================
--- index 2010-01-15 06:37:12 UTC (rev 4593)
+++ index 2010-01-15 07:00:11 UTC (rev 4594)
@@ -56466,16 +56466,17 @@
<dd>
- <ol><li><p>Replace the entry being updated with a new entry
- representing the new resource and its <code>Document</code>
- object and related state. The user agent may propagate state from
- the old entry to the new entry (e.g. scroll position).</li>
+ <ol><li><p>Replace the <code>Document</code> of the entry being
+ updated, and any other entries that referenced the same
+ document as that entry, with the new
+ <code>Document</code>.</li>
<li><p><a href=#traverse-the-history>Traverse the history</a> to the new
entry.</li>
</ol><p class=note>This can only happen if the entry being updated
- is no the <a href=#current-entry>current entry</a>. (It happens when the user
+ is no the <a href=#current-entry>current entry</a>, and can never happen with
+ <a href=#replacement-enabled>replacement enabled</a>. (It happens when the user
tried to traverse to a session history entry that no longer had
a <code>Document</code> object.)</p>
Modified: source
===================================================================
--- source 2010-01-15 06:37:12 UTC (rev 4593)
+++ source 2010-01-15 07:00:11 UTC (rev 4594)
@@ -63940,10 +63940,10 @@
<ol>
- <li><p>Replace the entry being updated with a new entry
- representing the new resource and its <code>Document</code>
- object and related state. The user agent may propagate state from
- the old entry to the new entry (e.g. scroll position).</p></li>
+ <li><p>Replace the <code>Document</code> of the entry being
+ updated, and any other entries that referenced the same
+ document as that entry, with the new
+ <code>Document</code>.</p></li>
<li><p><span>Traverse the history</span> to the new
entry.</p></li>
@@ -63951,7 +63951,8 @@
</ol>
<p class="note">This can only happen if the entry being updated
- is no the <span>current entry</span>. (It happens when the user
+ is no the <span>current entry</span>, and can never happen with
+ <span>replacement enabled</span>. (It happens when the user
tried to traverse to a session history entry that no longer had
a <code>Document</code> object.)</p>
More information about the Commit-Watchers
mailing list