- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Mon, 17 Nov 2008 15:25:08 +1300
On Mon, Nov 17, 2008 at 3:19 PM, Jonas Sicking <jonas at sicking.cc> wrote: > Ian Hickson wrote: > >> Video and audio playback is already extremely CPU intensive, we shouldn't >>> require the UA to burn extra cycles doing unnecessary work. >>> >> >> I agree. That was exactly the thinking behind the timeupdate event. It >> allows the UA to determine how fast to update the UI without hurting >> performance. Basically it puts the UA in charge of the performance critical >> aspects instead of hoping that the author will work it out. >> > > Though if all implementations are saying that it has the opposite effect > then clearly we need to look into if something went wrong :) > I don't think firing timeupdate on every frame is *that* bad for us, to be honest. 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/20081117/84a00d26/attachment.htm>
Received on Sunday, 16 November 2008 18:25:08 UTC