1345280 - A test case that we throttle animation that has no computed timing changes

Status: RESOLVED FIXED

(Core :: DOM: Animation, enhancement)

Description

[Hiroyuki Ikezoe (:hiro)]

Initially I did write a test case about this in bug 1344619, but it seems to me that this test case is not useful for bug 1344619.

After some thought, I noticed that this test case can be useful to check that we don't accidentally compose style on stylo because we don't check mElementsToRestyle when we compose style. So, for this test case, if we don't throttle animation that the computed timing is not changed on stylo, the test case will fail. A bad news is that we don't support time line markers on stylo yet.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=3987b25860bd8c83c2b8ec53157443d9cf551c85

Comment 1

[Hiroyuki Ikezoe (:hiro)]

Attachment: Bug 1345280 - A test case that makes sure we don't compose anmation styles while computed timing is not changed.

Review commit: https://reviewboard.mozilla.org/r/118010/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/118010/

Comment 2

[Boris Chiou [:boris]]

Comment on attachment 8844693 [details]
Bug 1345280 - A test case that makes sure we don't compose anmation styles while computed timing is not changed.

https://reviewboard.mozilla.org/r/118010/#review119870

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/03d9643f0fa0
A test case that makes sure we don't compose anmation styles while computed timing is not changed. r=boris

Comment 4

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/03d9643f0fa0