[html5] r4921 - [e] (0) let's be precise here Fixing http://www.w3.org/Bugs/Public/show_bug.cgi? [...]

whatwg at whatwg.org whatwg at whatwg.org
Wed Mar 31 12:47:27 PDT 2010


Author: ianh
Date: 2010-03-31 12:47:26 -0700 (Wed, 31 Mar 2010)
New Revision: 4921

Modified:
   complete.html
   index
   source
Log:
[e] (0) let's be precise here
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9180

Modified: complete.html
===================================================================
--- complete.html	2010-03-31 19:41:06 UTC (rev 4920)
+++ complete.html	2010-03-31 19:47:26 UTC (rev 4921)
@@ -24929,11 +24929,13 @@
    current playback 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
+   66Hz or slower than 4Hz (assuming the event handlers don't take
+   longer than 250ms to run). 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>
+
 <!--v2CUERANGE [beware - - nested comments]
    <li><p>If none of the <span title="cue range">cue ranges</span> in
    <var title="">current ranges</var> have their "active" boolean set

Modified: index
===================================================================
--- index	2010-03-31 19:41:06 UTC (rev 4920)
+++ index	2010-03-31 19:47:26 UTC (rev 4921)
@@ -24830,11 +24830,13 @@
    current playback 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
+   66Hz or slower than 4Hz (assuming the event handlers don't take
+   longer than 250ms to run). 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>
+
 <!--v2CUERANGE [beware - - nested comments]
    <li><p>If none of the <span title="cue range">cue ranges</span> in
    <var title="">current ranges</var> have their "active" boolean set

Modified: source
===================================================================
--- source	2010-03-31 19:41:06 UTC (rev 4920)
+++ source	2010-03-31 19:47:26 UTC (rev 4921)
@@ -26872,11 +26872,13 @@
    current playback 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
+   66Hz or slower than 4Hz (assuming the event handlers don't take
+   longer than 250ms to run). 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>
+
 <!--v2CUERANGE [beware - - nested comments]
    <li><p>If none of the <span title="cue range">cue ranges</span> in
    <var title="">current ranges</var> have their "active" boolean set




More information about the Commit-Watchers mailing list