no - all I'm saying is that in 48 of the 50x/sec you get called, you can trivially figure out that nothing needs to be done, so return quickly.<br><br><div class="gmail_quote">On Mon, Nov 17, 2008 at 3:05 PM, Jonas Sicking <span dir="ltr"><jonas@sicking.cc></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">Jeremy Doig wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
i would hope that repainting a progress bar that has not moved 50x/second would not be a normal implementation too. 2x/second seems more realistic (a 300s video with a 600 pixel-wide playbar).<br>
</blockquote>
<br></div>
Well, pages are most likely going to update the progress bar as often as we fire the event. So if we fire the event 50x/second then that's how often the progress bar will be updated.<br>
<br>
Sure, some pages might do things like only update on every 10th event, but this seems like a complex future since then content might start relying on that implementations use a specific firing rate.<br><font color="#888888">
<br>
/ Jonas<br>
</font></blockquote></div><br>