[html5] r3319 - [giw] (2) 'hashchange' is supposed to be async.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-06-25 18:19:49 -0700 (Thu, 25 Jun 2009)
New Revision: 3319

Modified:
   index
   source
Log:
[giw] (2) 'hashchange' is supposed to be async.

Modified: index
===================================================================
--- index	2009-06-26 00:52:58 UTC (rev 3318)
+++ index	2009-06-26 01:19:49 UTC (rev 3319)
@@ -51669,11 +51669,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

Modified: source
===================================================================
--- source	2009-06-26 00:52:58 UTC (rev 3318)
+++ source	2009-06-26 01:19:49 UTC (rev 3319)
@@ -58991,12 +58991,14 @@
    the <span>current entry</span>'s only by its fragment identifier,
    and the two share the same <code>Document</code> object, then
    first, if the <code>Document</code>'s <span>current document
-   readiness</span> is the string "complete", then <span>fire a simple
-   event</span> with the name <code
+   readiness</span> is the string "complete", then <span>queue a
+   task</span> to <span>fire a simple event</span> with the name <code
    title="event-hashchange">hashchange</code> at the <span>browsing
    context</span>'s <code>Window</code> object; and second, if the new
    URL has a fragment identifier, <span>scroll to the fragment
-   identifier</span>.</p></li>
+   identifier</span>. The <span>task source</span> for the task that
+   fires the <code title="event-hashchange">hashchange</code> event is
+   the <span>DOM manipulation task source</span>.</p></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