DescriptionWeb Animations: Timeline should not advance during task execution
Previously the animation clock was only frozen during animation frame
callbacks. This meant that the timeline was able to advance during other
tasks.
This patch allows the clock to advance once per task, either to the
compositor supplied frame start time or to an approximation of the next
expected frame time.
http://dev.w3.org/fxtf/web-animations/#script-execution-and-live-updates-to-the-model
This is a reland of r173583[1], the previous patch hit added assertions
due to double rounding issues, the new approach avoids these. Also ensures
that other unit tests see a non-zero currentTime (seen in some webkit_unit_test
runs on Android).
[1] https://src.chromium.org/viewvc/blink?view=rev&revision=173583
BUG=367903
TBR=abarth
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=174778
Patch Set 1 : Original patch #Patch Set 2 : Updated logic #Patch Set 3 : Rebase. #Patch Set 4 : #Patch Set 5 : Add back missing test changes. #Messages
Total messages: 13 (0 generated)
|