W3C home > Mailing lists > Public > public-css-testsuite@w3.org > February 2012

Re: [css3-transitions] [css3-animations] API for testing transitions and animations

From: Aryeh Gregor <ayg@aryeh.name>
Date: Tue, 14 Feb 2012 16:01:29 -0500
Message-ID: <CAKA+Axn+bhG60wF4Bu_e7ymEtCu3xiB6j-6WX9waQ7k=WFVTdA@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-css-testsuite@w3.org
On Tue, Feb 14, 2012 at 2:38 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> The setTimeout timer is almost certainly not very precise in practice.
> Especially if you want short timeouts.
>
> The animation timer may be better, as long as you keep in mind that it only
> fires at 60Hz or so.

So if we use requestAnimationFrame, it seems like that would let us
test transitions and animations and requestAnimationFrame pretty well,
right?

> Sure.  I'm saying there's a place for both sorts of test.

Right.  So I'll probably start on tests for transitions and animations
shortly.  My testing strategy will be

* Test computed style at the start, end, and iteration events, and
initially, and maybe also after everything should have finished.
* Test computed style using requestAnimationFrame.
* Test rendering using animated reftests.

I think that should give us decent coverage, no?
Received on Tuesday, 14 February 2012 21:02:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 14 February 2012 21:02:27 GMT