[html5] r8721 - [e] (0) Clarify seeking Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=26 [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Aug 26 17:03:26 PDT 2014
Author: ianh
Date: 2014-08-26 17:03:22 -0700 (Tue, 26 Aug 2014)
New Revision: 8721
Modified:
complete.html
index
source
Log:
[e] (0) Clarify seeking
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=26022
Affected topics: Video and Audio
Modified: complete.html
===================================================================
--- complete.html 2014-08-26 23:53:19 UTC (rev 8720)
+++ complete.html 2014-08-27 00:03:22 UTC (rev 8721)
@@ -23744,13 +23744,13 @@
this step is after <a href=#current-playback-position id=seeking:current-playback-position-4>current playback position</a>, then the adjusted <var>new
playback position</var> must also be after the <a href=#current-playback-position id=seeking:current-playback-position-5>current playback position</a>.</p>
- <p class=example>For example, the user agent could snap to the nearest key frame, so that it
+ <p class=example>For example, the user agent could snap to a nearby key frame, so that it
doesn't have to spend time decoding then discarding intermediate frames before resuming
playback.</p>
<li><p><a href=#queue-a-task id=seeking:queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event id=seeking:fire-a-simple-event>fire a simple event</a> named <code id=seeking:event-media-seeking><a href=#event-media-seeking>seeking</a></code> at the element.<li>
- <p>Set the <a href=#current-playback-position id=seeking:current-playback-position-6>current playback position</a> to the given <var>new playback
+ <p>Set the <a href=#current-playback-position id=seeking:current-playback-position-6>current playback position</a> to the <var>new playback
position</var>.</p>
<p class=note>If the <a href=#media-element id=seeking:media-element-3>media element</a> was <a href=#potentially-playing id=seeking:potentially-playing>potentially playing</a>
@@ -23763,9 +23763,9 @@
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 id=seeking:dom-media-currenttime-2><a href=#dom-media-currenttime>currentTime</a></code> attribute does not
- get updated asynchronously, as it returns the <a href=#official-playback-position id=seeking:official-playback-position>official playback position</a>, not the
- <a href=#current-playback-position id=seeking:current-playback-position-8>current playback position</a>.</p>
+ <p class=note>The <code id=seeking:dom-media-currenttime-2><a href=#dom-media-currenttime>currentTime</a></code> attribute returns
+ the <a href=#official-playback-position id=seeking:official-playback-position>official playback position</a>, not the <a href=#current-playback-position id=seeking:current-playback-position-8>current playback position</a>, and
+ therefore gets updated before script execution, separate from this algorithm.</p>
<li><p>Wait until the user agent has established whether or not the <a href=#media-data id=seeking:media-data>media data</a> for
the <var>new playback position</var> is available, and, if it is, until it has decoded
Modified: index
===================================================================
--- index 2014-08-26 23:53:19 UTC (rev 8720)
+++ index 2014-08-27 00:03:22 UTC (rev 8721)
@@ -23744,13 +23744,13 @@
this step is after <a href=#current-playback-position id=seeking:current-playback-position-4>current playback position</a>, then the adjusted <var>new
playback position</var> must also be after the <a href=#current-playback-position id=seeking:current-playback-position-5>current playback position</a>.</p>
- <p class=example>For example, the user agent could snap to the nearest key frame, so that it
+ <p class=example>For example, the user agent could snap to a nearby key frame, so that it
doesn't have to spend time decoding then discarding intermediate frames before resuming
playback.</p>
<li><p><a href=#queue-a-task id=seeking:queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event id=seeking:fire-a-simple-event>fire a simple event</a> named <code id=seeking:event-media-seeking><a href=#event-media-seeking>seeking</a></code> at the element.<li>
- <p>Set the <a href=#current-playback-position id=seeking:current-playback-position-6>current playback position</a> to the given <var>new playback
+ <p>Set the <a href=#current-playback-position id=seeking:current-playback-position-6>current playback position</a> to the <var>new playback
position</var>.</p>
<p class=note>If the <a href=#media-element id=seeking:media-element-3>media element</a> was <a href=#potentially-playing id=seeking:potentially-playing>potentially playing</a>
@@ -23763,9 +23763,9 @@
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 id=seeking:dom-media-currenttime-2><a href=#dom-media-currenttime>currentTime</a></code> attribute does not
- get updated asynchronously, as it returns the <a href=#official-playback-position id=seeking:official-playback-position>official playback position</a>, not the
- <a href=#current-playback-position id=seeking:current-playback-position-8>current playback position</a>.</p>
+ <p class=note>The <code id=seeking:dom-media-currenttime-2><a href=#dom-media-currenttime>currentTime</a></code> attribute returns
+ the <a href=#official-playback-position id=seeking:official-playback-position>official playback position</a>, not the <a href=#current-playback-position id=seeking:current-playback-position-8>current playback position</a>, and
+ therefore gets updated before script execution, separate from this algorithm.</p>
<li><p>Wait until the user agent has established whether or not the <a href=#media-data id=seeking:media-data>media data</a> for
the <var>new playback position</var> is available, and, if it is, until it has decoded
Modified: source
===================================================================
--- source 2014-08-26 23:53:19 UTC (rev 8720)
+++ source 2014-08-27 00:03:22 UTC (rev 8721)
@@ -30626,7 +30626,7 @@
this step is after <span>current playback position</span>, then the adjusted <var>new
playback position</var> must also be after the <span>current playback position</span>.</p>
- <p class="example">For example, the user agent could snap to the nearest key frame, so that it
+ <p class="example">For example, the user agent could snap to a nearby key frame, so that it
doesn't have to spend time decoding then discarding intermediate frames before resuming
playback.</p>
@@ -30637,7 +30637,7 @@
<li>
- <p>Set the <span>current playback position</span> to the given <var>new playback
+ <p>Set the <span>current playback position</span> to the <var>new playback
position</var>.</p>
<p class="note">If the <span>media element</span> was <span>potentially playing</span>
@@ -30654,9 +30654,9 @@
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>
+ <p class="note">The <code data-x="dom-media-currentTime">currentTime</code> attribute returns
+ the <span>official playback position</span>, not the <span>current playback position</span>, and
+ therefore gets updated before script execution, separate from this algorithm.</p>
</li>
More information about the Commit-Watchers
mailing list