On Fri, Nov 19, 2010 at 2:54 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> Darin Fisher:
> > How about just running the callback once the tab becomes visible again?
> It
> > will run, but just not unless there is reason to animate/paint.
>
> I can imagine a situation where you have an animation that goes for,
> say, 10 seconds, and once the animation finishes something else happens.
> The 1 second maximum period seems useful in this case, because you might
> make the tab visible again for a long time, but you expect the
> “something else” to happen. It’s pretty natural to do the checking for
> whether the animation has gone past its end time within the callback.
>
> (You might say though that for important “something elses”, these
> shouldn’t be keyed off an animation which might be throttled down
> severely.)
What's an acutal example where you might want this that couldn't just wait
until the tab was visible again? This use-case doesn't seem very common. As
you say, it's also probably not well met due to throttling.
Ojan