[html5] r2909 - [e] (0) mark issue regarding event inconsistency

whatwg at whatwg.org whatwg at whatwg.org
Wed Mar 25 02:45:19 PDT 2009


Author: ianh
Date: 2009-03-25 02:45:18 -0700 (Wed, 25 Mar 2009)
New Revision: 2909

Modified:
   index
   source
Log:
[e] (0) mark issue regarding event inconsistency

Modified: index
===================================================================
--- index	2009-03-25 08:44:43 UTC (rev 2908)
+++ index	2009-03-25 09:45:18 UTC (rev 2909)
@@ -20911,7 +20911,12 @@
 
   <ol><li><p>If the <a href=#media-element>media element</a> has a <code title=attr-media-loop><a href=#attr-media-loop>loop</a></code> attribute specified, then <a href=#dom-media-seek title=dom-media-seek>seek</a> to the <var><a href=#earliest-possible-position>earliest possible
    position</a></var> of the <a href=#media-resource>media resource</a> and abort these
-   steps.</li>
+   steps.</li> <!-- v2/v3: We should fire a 'looping' event here
+   to explain why this immediately fires a 'playing' event, otherwise
+   the 'playing' event that fires from the readyState going from
+   HAVE_CURRENT_DATA back to HAVE_FUTURE_DATA will seem inexplicable
+   (since the normally matching 'ended' given below event doesn't fire
+   in the loop case). -->
  
    <li><p>Stop playback.<p class=note>The <code title=dom-media-ended><a href=#dom-media-ended>ended</a></code> attribute becomes
    true.</li>

Modified: source
===================================================================
--- source	2009-03-25 08:44:43 UTC (rev 2908)
+++ source	2009-03-25 09:45:18 UTC (rev 2909)
@@ -22729,7 +22729,12 @@
    title="attr-media-loop">loop</code> attribute specified, then <span
    title="dom-media-seek">seek</span> to the <var>earliest possible
    position</var> of the <span>media resource</span> and abort these
-   steps.</p></li>
+   steps.</p></li> <!-- v2/v3: We should fire a 'looping' event here
+   to explain why this immediately fires a 'playing' event, otherwise
+   the 'playing' event that fires from the readyState going from
+   HAVE_CURRENT_DATA back to HAVE_FUTURE_DATA will seem inexplicable
+   (since the normally matching 'ended' given below event doesn't fire
+   in the loop case). -->
  
    <li><p>Stop playback.</p><p class="note">The <code
    title="dom-media-ended">ended</code> attribute becomes




More information about the Commit-Watchers mailing list