hixie: Define how location.href='foo' aborts parsing. (whatwg r5643)

hixie: Define how location.href='foo' aborts parsing. (whatwg r5643)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4520&r2=1.4521&f=h
http://html5.org/tools/web-apps-tracker?from=5642&to=5643

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4520
retrieving revision 1.4521
diff -u -d -r1.4520 -r1.4521
--- Overview.html 20 Oct 2010 19:14:33 -0000 1.4520
+++ Overview.html 22 Oct 2010 23:07:50 -0000 1.4521
@@ -321,7 +321,7 @@
 
    <h1>HTML5</h1>
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-20-october-2010">Editor's Draft 20 October 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-22-october-2010">Editor's Draft 22 October 2010</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -451,7 +451,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 20 October 2010 Editor's Draft.
+  This specification is the 22 October 2010 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
   actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
   group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -7386,7 +7386,8 @@
   <p>A <code><a href="#document">Document</a></code> is said to have an <dfn id="active-parser">active
   parser</dfn> if it is associated with an <a href="#html-parser">HTML parser</a> or
   an <a href="#xml-parser">XML parser</a> that has not yet been <a href="#stop-parsing" title="stop
-  parsing">stopped</a> or aborted.</p>
+  parsing">stopped</a> or <a href="#abort-a-parser" title="abort a
+  parser">aborted</a>.</p>
 
   <p>The <dfn id="dom-document-readystate" title="dom-document-readyState"><code>readyState</code></dfn> IDL
   attribute must, on getting, return the <a href="#current-document-readiness">current document
@@ -9993,9 +9994,8 @@
    <code><a href="#document">Document</a></code> object, with the <var title="">recycle</var>
    parameter set to true.</li>
 
-   <li><p>If the document has an <a href="#active-parser">active parser</a>, then
-   <a href="#abort-an-html-parser" title="abort an HTML parser">abort that
-   parser</a>.</li>
+   <li><p><a href="#abort-a-document" title="abort a document">Abort</a> the
+   <code><a href="#document">Document</a></code>.</li>
 
    <li><p>Unregister all event listeners registered on the
    <code><a href="#document">Document</a></code> node and its descendants.</p>
@@ -37451,7 +37451,7 @@
 
   </div><div class="impl">
 
-  <h5 id="form-submission-algorithm"><span class="secno">4.10.22.3 </span>Form submission algorithm</h5>
+  <h5 id="form-submission-algorithm"><span class="secno">4.10.22.3 </span>Form submission algorithm</h5><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/138">ISSUE-138</a> (mutate-action) blocks progress to Last Call</span></p>
 
   <p>When a <code><a href="#the-form-element">form</a></code> element <var title="">form</var> is <dfn id="concept-form-submit" title="concept-form-submit">submitted</dfn> from an element <var title="">submitter</var> (typically a button), optionally with a
   <var title="">scripted-submit</var> flag set, the user agent must
@@ -46048,6 +46048,10 @@
    <li><p>Cancel <em>any</em> preexisting attempt to navigate the
    <a href="#browsing-context">browsing context</a>.</li>
 
+   <li><p><a href="#abort-a-document" title="abort a document">Abort</a> the
+   <a href="#active-document">active document</a> of the <a href="#browsing-context">browsing
+   context</a>.</li>
+
    <li><p>If the new resource is to be handled using a mechanism that
    does not affect the browsing context, e.g. ignoring the navigation
    request altogether because the specified scheme is not one of the
@@ -47213,12 +47217,32 @@
 
   <h4 id="aborting-a-document-load"><span class="secno">5.5.11 </span>Aborting a document load</h4>
 
-  <p>If the user cancels any instance of the <a href="#fetch" title="fetch">fetching algorithm</a> in the context of a
-  <code><a href="#document">Document</a></code> in a <a href="#browsing-context">browsing context</a>, then, if
-  that <code><a href="#document">Document</a></code> is an <a href="#active-document">active document</a>, the
-  user agent must <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple
+  <p>If a <code><a href="#document">Document</a></code> is <dfn id="abort-a-document" title="abort a
+  document">aborted</dfn>, the user agent must run the following
+  steps:</p>
+
+  <ol><li><p><a href="#abort-a-document" title="abort a document">Abort</a> the <a href="#active-document" title="active document">active documents</a> of every
+   <a href="#child-browsing-context">child browsing context</a>.</li>
+
+   <li><p>Cancel any instances of the <a href="#fetch" title="fetch">fetch</a>
+   algorithm in the context of this <code><a href="#document">Document</a></code>, discarding
+   any <a href="#concept-task" title="concept-task">tasks</a> <a href="#queue-a-task" title="queue a
+   task">queued</a> for them, and discarding any further data
+   received from the network for them.</li>
+
+   <li><p>If the <code><a href="#document">Document</a></code> has an <a href="#active-parser">active
+   parser</a>, then <a href="#abort-a-parser" title="abort a parser">abort that
+   parser</a>.</li>
+
+   <!-- we could also stop all script, or stop animations -->
+
+  </ol><p>User agents may allow users to explicitly invoke the <a href="#abort-a-document" title="abort a document">abort a document</a> algorithm for a
+  <code><a href="#document">Document</a></code>. If the user does so, then, if that
+  <code><a href="#document">Document</a></code> is an <a href="#active-document">active document</a>, the user
+  agent should <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple
   event</a> named <code title="event-abort">abort</code> at that
-  <code><a href="#document">Document</a></code>'s <code><a href="#window">Window</a></code> object.</p>
+  <code><a href="#document">Document</a></code>'s <code><a href="#window">Window</a></code> object before invoking
+  the <a href="#abort-a-document" title="abort a document">abort</a> algorithm.</p>
 
   <!-- I'd love to make this more precise, anyone have any suggestions
   on what it should say? -->
@@ -62360,8 +62384,8 @@
    <li><p>The <code><a href="#document">Document</a></code> is now <dfn id="completely-loaded">completely
    loaded</dfn>.</li>
 
-  </ol><p>When the user agent is to <dfn id="abort-an-html-parser">abort an HTML parser</dfn>, it
-  must run the following steps:</p>
+  </ol><p>When the user agent is to <dfn id="abort-a-parser">abort a parser</dfn>, it must run
+  the following steps:</p>
 
   <ol><li><p>Throw away any pending content in the <a href="#the-input-stream">input
    stream</a>, and discard any future content that would have been
@@ -62371,8 +62395,11 @@
    elements</a>.</li>
 
    <!-- anything else? this is things that happen when you call
-   document.open() on a document that's still being parsed. Should the
-   pending scripts be blown away or anything? -->
+   document.open() on a document that's still being parsed, or when
+   you navigate a document that's still parsing, or navigate the
+   parent of a frame with a document that's still parsing, or the user
+   hits "stop". Should the pending scripts be blown away or anything?
+   -->
 
   </ol><p>Except where otherwise specified, the <a href="#task-source">task source</a>
   for the <a href="#concept-task" title="concept-task">tasks</a> mentioned in this
@@ -63231,7 +63258,9 @@
 
   <p>When an <a href="#xml-parser">XML parser</a> reaches the end of its input, it
   must <a href="#stop-parsing">stop parsing</a>, following the same rules as the
-  <a href="#html-parser">HTML parser</a>.</p>
+  <a href="#html-parser">HTML parser</a>. An <a href="#xml-parser">XML parser</a> can also be
+  <a href="#abort-a-parser" title="abort a parser">aborted</a>, which must again by
+  done in the same way as for an <a href="#html-parser">HTML parser</a>.</p>
 
   <p>For the purposes of conformance checkers, if a resource is
   determined to be in <a href="#the-xhtml-syntax">the XHTML syntax</a>, then it is an
@@ -71904,7 +71933,7 @@
 
 
 
-  </dl><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><!-- ACKS --><p>Thanks to
+  </dl><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/139">ISSUE-139</a> (ack-microdata) blocks progress to Last Call</span></p><!-- ACKS --><p>Thanks to
 
   Aankhen,
   Aaron Boodman,

Received on Friday, 22 October 2010 23:08:44 UTC