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

[whatwg] Video Element Events? - Use Case: Custom Progress Bar

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 18 Nov 2008 12:19:06 +1300
Message-ID: <11e306600811171519g7276bf42m455cd7a07da1f294@mail.gmail.com>
On Tue, Nov 18, 2008 at 12:09 PM, Antti Koivisto <antti at apple.com> wrote:

> On 16.11.2008, at 16:16, Ian Hickson wrote:
>
>  With polling, the polling will miss key points, e.g. when the playback
>> loops, which will result in the UI appearing to lag behind the playback.
>> It will also cause higher processing cost while there is no need to send
>> updates, e.g. while seeking or waiting for data, times where you really
>> don't want extra load.
>>
>
> The earlier iteration of the spec already fired timeupdate events on all
> discontinuous changes in time. How would this event flood be an improvement
> over that?


That makes a lot more sense than limiting the timeupdate period. Firing
timeupdate on discontinuous changes and requiring apps to also use a regular
timer to get periodic updates sounds reasonable to me.

- Requiring events on every frame might make some playback optimizations
> impossible (by requiring constant activation of the web engine thread during
> playback).
>

Can you be more specific?

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20081118/db07fc27/attachment.htm>
Received on Monday, 17 November 2008 15:19:06 UTC

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