hixie: Correct how 'entry update' is to happen to also update the other entries that referenced the document, and to not blow away state objects. (whatwg r4594)

hixie: Correct how 'entry update' is to happen to also update the other
entries that referenced the document, and to not blow away state
objects. (whatwg r4594)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3670&r2=1.3671&f=h
http://html5.org/tools/web-apps-tracker?from=4593&to=4594

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3670
retrieving revision 1.3671
diff -u -d -r1.3670 -r1.3671
--- Overview.html 15 Jan 2010 06:37:18 -0000 1.3670
+++ Overview.html 15 Jan 2010 07:00:17 -0000 1.3671
@@ -44139,16 +44139,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>

Received on Friday, 15 January 2010 07:01:06 UTC