spec/Overview.html 1.2015 2844 Give up on 205. Define how session histo

Give up on 205. Define how session history updates work without breaking
scripts. (whatwg r2844)

Fragment identifiers: If the absolute URL of the new resource is the same as the address of the active document of the browsing context being navigated, ignoring any <fragment> components of those URLs, and the new resource is to be fetched using HTTP GET or equivalent, then navigate to that fragment identifier and abort these steps.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2015.html#navigate-fragid-step
5.10.2 Page load processing model for HTML files
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2015.html#read-html
replacement enabled
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2015.html#replacement-enabled
Non-document content: If, given type, the new resource is to be handled by displaying some sort of inline content, e.g. a native rendering of the content, an error message because the specified type is not supported, or an inline prompt to allow the user to select a registered handler for the given type, then display the inline content and abort these steps.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2015.html#navigate-non-Document
update the session history with the new page
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2015.html#update-the-session-history-with-the-new-page

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2014&r2=1.2015&f=h
http://html5.org/tools/web-apps-tracker?from=2843&to=2844

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2014
retrieving revision 1.2015
diff -u -d -r1.2014 -r1.2015
--- Overview.html 19 Feb 2009 11:12:26 -0000 1.2014
+++ Overview.html 19 Feb 2009 11:30:30 -0000 1.2015
@@ -32780,7 +32780,10 @@
      <li>Network errors</li>
     </ul></div>
    
-    <!-- XXX should we define 205 processing here? e.g. reset all forms? -->
+    <!-- theorectically, HTTP 205 processing would occur here,
+    resetting all forms with no other effect. However, it seems nobody
+    actually wants to use this ability, so requiring it here seems
+    like unnecessary work. -->
 
     <p>HTTP 401 responses that do not include a challenge recognised
     by the user agent must be processed as if they had no challenge,
@@ -32871,12 +32874,8 @@
   </ol><p>Some of the sections below, to which the above algorithm defers
   in certain cases, require the user agent to <dfn id=update-the-session-history-with-the-new-page>update the session
   history with the new page</dfn>. When a user agent is required to do
-  this, it must follows the set of steps given below that is
-  appropriate for the situation at hand. From the point of view of any
-  script, these steps must occur atomically.<ol><li><p class=XXX>pause for scripts -- but don't use the
-   "pause" definition since that involves not running script!</li>
-
-   <li><p><a href=#unload-a-document title="unload a document">Unload</a> the
+  this, it must <a href=#queue-a-task>queue a task</a> to run the following
+  steps:<ol><li><p><a href=#unload-a-document title="unload a document">Unload</a> the
    <code>Document</code> object of the <a href=#current-entry>current entry</a>,
    with the <var title="">recycle</var> parameter set to
    false.</li>
@@ -32945,7 +32944,8 @@
 
     </ol></li>
 
-  </ol><h4 id=read-html><span class=secno>5.10.2 </span><dfn title=navigate-html>Page load processing model for HTML files</dfn></h4><p>When an HTML document is to be loaded in a <a href=#browsing-context>browsing
+  </ol><p>The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#networking-task-source>networking task
+  source</a>.<h4 id=read-html><span class=secno>5.10.2 </span><dfn title=navigate-html>Page load processing model for HTML files</dfn></h4><p>When an HTML document is to be loaded in a <a href=#browsing-context>browsing
   context</a>, the user agent must create a <code>Document</code>
   object, mark it as being an <a href=#html-documents title="HTML documents">HTML
   document</a>, create an <a href=#html-parser>HTML parser</a>, associate it

Received on Thursday, 19 February 2009 11:34:58 UTC