[html5] r8575 - [e] (0) Clarify the interaction of looping and seeking. Fixing https://www.w3.or [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Apr 14 14:53:15 PDT 2014
Author: ianh
Date: 2014-04-14 14:53:07 -0700 (Mon, 14 Apr 2014)
New Revision: 8575
Modified:
complete.html
index
source
Log:
[e] (0) Clarify the interaction of looping and seeking.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=24955
Affected topics: Video and Audio
Modified: complete.html
===================================================================
--- complete.html 2014-04-14 21:46:18 UTC (rev 8574)
+++ complete.html 2014-04-14 21:53:07 UTC (rev 8575)
@@ -27387,7 +27387,7 @@
the synthesized speech generated for a cue is longer than the time between the <a href=#text-track-cue-start-time>text track
cue start time</a> and the <a href=#text-track-cue-end-time>text track cue end time</a>.</p>
- <hr><p>When the <a href=#current-playback-position>current playback position</a> reaches the end of the <a href=#media-resource>media
+ <hr><!--CLEANUP--><p id=reaches-the-end>When the <a href=#current-playback-position>current playback position</a> reaches the end of the <a href=#media-resource>media
resource</a> when the <a href=#direction-of-playback>direction of playback</a> is forwards, then the user agent must
follow these steps:</p>
@@ -27889,6 +27889,11 @@
fired</a> at the element.</p> <!-- also, timeupdate -->
<!-- also, it will do the "report the controller state" thing -->
+ <p class=note>This step sets the <a href=#current-playback-position>current playback position</a>, and thus can
+ immediately trigger other conditions, such as the rules regarding when playback "<a href=#reaches-the-end>reaches the end of the media resource</a>" (part of the logic that
+ handles looping), even before the user agent is actually able to render the media data for that
+ position (as determined in the next step).</p>
+
<p class=note>The <code title=dom-media-currentTime><a href=#dom-media-currenttime>currentTime</a></code> attribute does not
get updated asynchronously, as it returns the <a href=#official-playback-position>official playback position</a>, not the
<a href=#current-playback-position>current playback position</a>.</p>
Modified: index
===================================================================
--- index 2014-04-14 21:46:18 UTC (rev 8574)
+++ index 2014-04-14 21:53:07 UTC (rev 8575)
@@ -27387,7 +27387,7 @@
the synthesized speech generated for a cue is longer than the time between the <a href=#text-track-cue-start-time>text track
cue start time</a> and the <a href=#text-track-cue-end-time>text track cue end time</a>.</p>
- <hr><p>When the <a href=#current-playback-position>current playback position</a> reaches the end of the <a href=#media-resource>media
+ <hr><!--CLEANUP--><p id=reaches-the-end>When the <a href=#current-playback-position>current playback position</a> reaches the end of the <a href=#media-resource>media
resource</a> when the <a href=#direction-of-playback>direction of playback</a> is forwards, then the user agent must
follow these steps:</p>
@@ -27889,6 +27889,11 @@
fired</a> at the element.</p> <!-- also, timeupdate -->
<!-- also, it will do the "report the controller state" thing -->
+ <p class=note>This step sets the <a href=#current-playback-position>current playback position</a>, and thus can
+ immediately trigger other conditions, such as the rules regarding when playback "<a href=#reaches-the-end>reaches the end of the media resource</a>" (part of the logic that
+ handles looping), even before the user agent is actually able to render the media data for that
+ position (as determined in the next step).</p>
+
<p class=note>The <code title=dom-media-currentTime><a href=#dom-media-currenttime>currentTime</a></code> attribute does not
get updated asynchronously, as it returns the <a href=#official-playback-position>official playback position</a>, not the
<a href=#current-playback-position>current playback position</a>.</p>
Modified: source
===================================================================
--- source 2014-04-14 21:46:18 UTC (rev 8574)
+++ source 2014-04-14 21:53:07 UTC (rev 8575)
@@ -29220,7 +29220,8 @@
<hr>
- <p>When the <span>current playback position</span> reaches the end of the <span>media
+<!--CLEANUP-->
+ <p id="reaches-the-end">When the <span>current playback position</span> reaches the end of the <span>media
resource</span> when the <span>direction of playback</span> is forwards, then the user agent must
follow these steps:</p>
@@ -29827,6 +29828,12 @@
fired</a> at the element.</p> <!-- also, timeupdate -->
<!-- also, it will do the "report the controller state" thing -->
+ <p class="note">This step sets the <span>current playback position</span>, and thus can
+ immediately trigger other conditions, such as the rules regarding when playback "<a
+ href="#reaches-the-end">reaches the end of the media resource</a>" (part of the logic that
+ handles looping), even before the user agent is actually able to render the media data for that
+ position (as determined in the next step).</p>
+
<p class="note">The <code data-x="dom-media-currentTime">currentTime</code> attribute does not
get updated asynchronously, as it returns the <span>official playback position</span>, not the
<span>current playback position</span>.</p>
More information about the Commit-Watchers
mailing list