On Mon, Nov 17, 2008 at 5:09 PM, Antti Koivisto <span dir="ltr"><<a href="mailto:antti@apple.com">antti@apple.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 16.11.2008, at 16:16, Ian Hickson wrote:<br>
<div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You don't have to fire the event if nobody is listening for it. (Browsers<br>
likely already have this implementation for mutation events if nothing<br>
else, so this shouldn't be that difficult to implement.)<br>
</blockquote>
<br></div>
If I want to update a time display once per second (which I think is fairly typical) why should I listen to a flood of events 60 times per second? On some devices those events and the Javascript that needs to run to filter them might consume substantial portion of the available CPU capacity.</blockquote>
<div><br>Keep in mind what we're dealing with here. This isn't some trivial Javascript timer firing off events at 60Hz. This is a full <video> element. If a little "i++; if( i%60 == 0) {code}" is killing the CPU, then that device isn't capable of playing a <video> either.<br>
</div></div><br>~TJ<br>