spec/Overview.html 1.2024 2853 Ugh. Fix the order of events in the case

Ugh. Fix the order of events in the case of autoplay. (whatwg r2853)

If this is the first time this occurs for this media element since the load() algorithm was last invoked, the user agent must queue a task to fire a simple event called loadeddata at the element.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2024.html#fire-loadeddata

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2023&r2=1.2024&f=h
http://html5.org/tools/web-apps-tracker?from=2852&to=2853

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2023
retrieving revision 1.2024
diff -u -d -r1.2023 -r1.2024
--- Overview.html 23 Feb 2009 08:49:09 -0000 1.2023
+++ Overview.html 23 Feb 2009 08:55:43 -0000 1.2024
@@ -15810,16 +15810,16 @@
 
     <p>If the previous ready state was <code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code> or
     less, the user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
-    a simple event</a> called <code title=event-canplay><a href=#event-canplay>canplay</a></code>.</p>
-
-    <p>In either case, the user agent must then <a href=#queue-a-task>queue a
-    task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-canplaythrough><a href=#event-canplaythrough>canplaythrough</a></code>.</p>
+    a simple event</a> called <code title=event-canplay><a href=#event-canplay>canplay</a></code>, and, if the element is also
+    <a href=#potentially-playing>potentially playing</a>, <a href=#queue-a-task>queue a task</a> to
+    <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-playing><a href=#event-playing>playing</a></code>.</p>
 
     <p>If the <a href=#autoplaying-flag>autoplaying flag</a> is true, and the <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> attribute is true, and the
     <a href=#media-element>media element</a> has an <code title=attr-media-autoplay><a href=#attr-media-autoplay>autoplay</a></code> attribute specified,
-    then the user agent may also set the <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> attribute to false and
+    then the user agent may also set the <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> attribute to false,
     <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
-    called <code title=event-play><a href=#event-play>play</a></code>.</p>
+    called <code title=event-play><a href=#event-play>play</a></code>, and <a href=#queue-a-task>queue a
+    task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-playing><a href=#event-playing>playing</a></code>.</p>
 
     <p class=note>User agents are not required to autoplay, and it
     is suggested that user agents honor user preferences on the
@@ -15827,10 +15827,8 @@
     using script to force the video to play, so as to allow the user
     to override the behavior if so desired.</p>
 
-    <p>If the element is now <a href=#potentially-playing>potentially playing</a>, and the
-    previous ready state was <code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code> or
-    less, the user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
-    a simple event</a> called <code title=event-playing><a href=#event-playing>playing</a></code>.</p>
+    <p>In any case, the user agent must finally <a href=#queue-a-task>queue a
+    task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-canplaythrough><a href=#event-canplaythrough>canplaythrough</a></code>.</p>
 
    </dd>

Received on Monday, 23 February 2009 08:59:22 UTC