W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2009

[whatwg] What is the purpose of timeupdate?

From: Simon Pieters <simonp@opera.com>
Date: Fri, 06 Nov 2009 23:52:42 +0100
Message-ID: <op.u2zwh4myidj3kv@simon-pieterss-macbook.local>
On Fri, 06 Nov 2009 18:11:18 +0100, Brian Campbell  
<brian.p.campbell at dartmouth.edu> wrote:

>> Brian, since Firefox is doing what you proposed -- can you think of any  
>> other issues with its current implementation?  What about for audio  
>> files?
>
> The way Firefox works is fine for me. I haven't yet tested it with audio  
> only, but something around 25 or 30 updates per second would work fine  
> for all use cases that I have; 15 updates per second is about the  
> minimum I'd consider useful for synchronizing one off events like  
> bullets or slide transitions (this is for stuff where you want good,  
> tight sync for stuff with high production values), and while animations  
> would work at that rate, they'd be pretty jerky.

What if you have a video with say one frame per second? Unless I'm  
mistaken Firefox will still fire timeupdate once per frame. (The spec says  
you have to fire at least every 250ms.)

-- 
Simon Pieters
Opera Software
Received on Friday, 6 November 2009 14:52:42 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:18 UTC