- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 10 Sep 2010 21:05:32 +1000
On Fri, Sep 10, 2010 at 7:28 PM, Biju <bijumaillist at gmail.com> wrote: > https://bugzilla.mozilla.org/show_bug.cgi?id=571822 > > Firefox fires the timeupdate event once per frame. > > Safari 5 and Chrome 6 fire every 250ms. Opera 10.50 fires every 200ms. > > > Now in firefox bug 571822 they are changing Firefox fires the > timeupdate event at every 250ms > > But this takes away control of somebody who want to do some image > process on every frame, as well as miss frames. > > So can we have a "newFrame" event and/or a "minTimeupdate" property to > say what should be the minimum time interval between consecutive > timeupdate event. > If we have a newFrame event, might it be an idea to actually hand over the frame data (audio + video) in the event? I would think that only ppl that want to do manipulations on the media data want to have that kind of resolution and it might be more efficient to just provide the data with the event? Incidentally: What use case did you have in mind, Biju? Cheers, Silvia. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100910/3a6e6ffc/attachment.htm>
Received on Friday, 10 September 2010 04:05:32 UTC