'hashchange' is supposed to be async. (whatwg r3319)

'hashchange' is supposed to be async. (whatwg r3319)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2458&r2=1.2459&f=h
http://html5.org/tools/web-apps-tracker?from=3318&to=3319

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2458
retrieving revision 1.2459
diff -u -d -r1.2458 -r1.2459
--- Overview.html 25 Jun 2009 23:19:23 -0000 1.2458
+++ Overview.html 26 Jun 2009 01:19:55 -0000 1.2459
@@ -167,7 +167,7 @@
    <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>
    <!--ZZZ:-->
    <!--<h2 class="no-num no-toc">W3C Working Draft 23 April 2009</h2>-->
-   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 25 June 2009</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 26 June 2009</h2>
    <!--:ZZZ-->
    <dl><!-- ZZZ: update the month/day (twice), (un)comment out
     <dt>This Version:</dt>
@@ -260,7 +260,7 @@
   track.
   <!--ZZZ:-->
   <!--This specification is the 23 April 2009 Working Draft.-->
-  This specification is the 25 June 2009 Editor's Draft.
+  This specification is the 26 June 2009 Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href="http://www.whatwg.org/">WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -46543,11 +46543,13 @@
    the <a href="#current-entry">current entry</a>'s only by its fragment identifier,
    and the two share the same <code>Document</code> object, then
    first, if the <code>Document</code>'s <a href="#current-document-readiness">current document
-   readiness</a> is the string "complete", then <a href="#fire-a-simple-event">fire a simple
-   event</a> with the name <code title="event-hashchange">hashchange</code> at the <a href="#browsing-context">browsing
+   readiness</a> is the string "complete", then <a href="#queue-a-task">queue a
+   task</a> to <a href="#fire-a-simple-event">fire a simple event</a> with the name <code title="event-hashchange">hashchange</code> at the <a href="#browsing-context">browsing
    context</a>'s <code><a href="#window">Window</a></code> object; and second, if the new
    URL has a fragment identifier, <a href="#scroll-to-the-fragment-identifier">scroll to the fragment
-   identifier</a>.</li>
+   identifier</a>. The <a href="#task-source">task source</a> for the task that
+   fires the <code title="event-hashchange">hashchange</code> event is
+   the <a href="#dom-manipulation-task-source">DOM manipulation task source</a>.</li>
 
    <li><p>User agents may also update other aspects of the document
    view when the location changes in this way, for instance the scroll

Received on Friday, 26 June 2009 01:20:57 UTC