Brian Birtles efd02d2a25 Bug 1339648 - Fix flaky file_transitions_replacement_on_busy_frame.html test; r=hiro
There are two issues with this test:

(a) It fails to flush style when it intends to trigger the first transition.

    Specifically, `getComputedStyle(div)` alone does not flush style. Instead we
    need `getComputedStyle(div).transform`.

    This patch replaces that line with a call to `div.getAnimations()` which
    *does* flush style ensuring the first transition is triggered.

(b) It fails to ensure that the first transition has progressed past the first
    frame on the main thread before triggering the second transition.

    If the first transition is still on its first frame, the computed value of
    'transform' will be 'matrix(1, 0, 0, 1, 0, 0)'. If we then update the
    specified value of 'transform' to 'translateX(0px)', no transition will be
    generated (although the first transition will be canceled) since there is no
    change.

    This patch fixes that by making the end point of the second transition NOT
    match the start point of the first transition (and not be somewhere inside
    the range of the first transition).

As an extra precautionary measure, to be sure that the animation has started
progressing on both the main thread and compositor, this patch alters the
initial wait condition for the first transition to also wait on the first
transition's ready promise.

MozReview-Commit-ID: E1OJuHBSMfr

--HG--
extra : rebase_source : aede0fa00f261e1c7d1be61857b6fd0537a0f7e7
2017-08-23 18:17:31 +09:00
..