Open Bug 1112957 Opened 5 years ago Updated 4 years ago

Rewrite animation tests that rely on nsDOMWindowUtils.advanceTimeAndRefresh() to asynchronously wait for animations to start

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set

Tracking

()

People

(Reporter: birtles, Unassigned)

Details

Bug 927349 makes animations start once their first frame renders. A lot of tests, however, assume animations start immediately. Rather an updating all these tests bug 927349 simply changes the behavior of nsDOMWindowUtils.advanceTimeAndRefresh to look for any animations that are waiting to start and then forcing them to start immediately. This allows existing tests to continue working as normal.

However, it means that the code path followed when playing animations regularly differs from when we test them.

Ideally we should update these tests to asynchronously wait until each animation has started. Alternatively, when enough of the Web Animations API is available, we could probably rewrite a lot of them to no longer use nsDOMWindowUtils.advanceTimeAndRefresh at all.
You need to log in before you can comment on or make changes to this bug.