Address timeouts in composited CSS animations event dispatch test
There are no restrictions on how quickly the client agent needs to respond to a pending play-state change. For non-composited animations the ready promise is resolved on commit of the animation frame; however, for a composited animation, the process is delayed until receiving a start-time notification from the compositor. The event dispatch test previously waited up to 2 animations frames, which is adequate for non-composited tests since the events trigger on the next frame. For composited tests, we need to first wait for the animation to be ready if in a pending state. Once the ready promise is resolved, a two frame time limit is sufficient for the remainder of the steps. Tested with 300 repetitions of the flaking tests in the virtual/threaded environment. Bug: 1064065 Change-Id: Ic4975d5885d3513c5c1b53d755757c0adcc027c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341803Reviewed-by:Xida Chen <xidachen@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#795918}
Showing
Please register or sign in to comment