Isn't there a 16ms contract for raf in some browsers? Specifically, if you do your work in under 16ms, it will get the next (known) timeslice? Yehuda Katz (ph) 718.877.1325 On Wed, May 9, 2012 at 11:36 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 5/9/12 2:20 PM, Yehuda Katz wrote: > >> In this case, shouldn't the time be "the time that the animations will >> be presented on >> the screen". >> > > That would be ideal, yes. Hard to do, of course, since the request > callback has to run before the animation is presented on the screen and the > browser has no way to know how long it'll take to run.... > > In practice, for synchronizing animations with each other it's more > important that the same time be used for all animations than what exactly > that time means. For making a particular animation look smooth, of course, > the meaning of the time might matter. > > -Boris >
Received on Wednesday, 9 May 2012 21:28:15 UTC