- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 25 Mar 2009 09:45:27 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv23990
Modified Files:
Overview.html
Log Message:
mark issue regarding event inconsistency (whatwg r2909)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2076
retrieving revision 1.2077
diff -u -d -r1.2076 -r1.2077
--- Overview.html 25 Mar 2009 08:44:48 -0000 1.2076
+++ Overview.html 25 Mar 2009 09:45:24 -0000 1.2077
@@ -18287,7 +18287,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>
Received on Wednesday, 25 March 2009 09:45:39 UTC