[html5] r2407 - [gow] (2) Specify how frequently the timeupdate event should fire.
whatwg at whatwg.org
whatwg at whatwg.org
Sun Nov 16 17:11:56 PST 2008
Author: ianh
Date: 2008-11-16 17:11:55 -0800 (Sun, 16 Nov 2008)
New Revision: 2407
Modified:
index
source
Log:
[gow] (2) Specify how frequently the timeupdate event should fire.
Modified: index
===================================================================
--- index 2008-11-17 01:06:24 UTC (rev 2406)
+++ index 2008-11-17 01:11:55 UTC (rev 2407)
@@ -18161,13 +18161,21 @@
steps.</li>
<li><p>If the time was reached through the usual monotonic increase
- of the current playback position during normal playback, 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-timeupdate><a href=#event-timeupdate>timeupdate</a></code> at the element. (In the
+ of the current playback position during normal playback, and if the
+ user agent has not fired a <code title=event-timeupdate><a href=#event-timeupdate>timeupdate</a></code> event at the element in
+ the past 15 to 250ms, 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-timeupdate><a href=#event-timeupdate>timeupdate</a></code> at the element. (In the
other cases, such as explicit seeks, relevant events get fired as
part of the overall process of changing the current playback
- position.)</li>
+ position.)</p>
+ <p class=note>The event thus is not to be fired faster than about
+ 66Hz or slower than 4Hz. User agents are encouraged to vary the
+ frequency of the event based on the system load and the average
+ cost of processing the event each time, so that the UI updates are
+ not any more frequent than the user agent can comfortably handle
+ while decoding the video.</li>
+
<li><p>If the time was reached through the usual monotonic increase
of the current playback position during normal playback, and there
are <a href=#cue-range title="cue range">cue ranges</a> in <var title="">other ranges</var> that have both their "active" boolean
Modified: source
===================================================================
--- source 2008-11-17 01:06:24 UTC (rev 2406)
+++ source 2008-11-17 01:11:55 UTC (rev 2407)
@@ -19671,14 +19671,23 @@
steps.</p></li>
<li><p>If the time was reached through the usual monotonic increase
- of the current playback position during normal playback, the user
- agent must then <span>queue a task</span> to <span>fire a simple
- event</span> called <code
+ of the current playback position during normal playback, and if the
+ user agent has not fired a <code
+ title="event-timeupdate">timeupdate</code> event at the element in
+ the past 15 to 250ms, the user agent must then <span>queue a
+ task</span> to <span>fire a simple event</span> called <code
title="event-timeupdate">timeupdate</code> at the element. (In the
other cases, such as explicit seeks, relevant events get fired as
part of the overall process of changing the current playback
- position.)</p></li>
+ position.)</p>
+ <p class="note">The event thus is not to be fired faster than about
+ 66Hz or slower than 4Hz. User agents are encouraged to vary the
+ frequency of the event based on the system load and the average
+ cost of processing the event each time, so that the UI updates are
+ not any more frequent than the user agent can comfortably handle
+ while decoding the video.</p></li>
+
<li><p>If the time was reached through the usual monotonic increase
of the current playback position during normal playback, and there
are <span title="cue range">cue ranges</span> in <var
More information about the Commit-Watchers
mailing list