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

RESOLVED FIXED in Firefox 55

Status

()

Core
DOM: Animation
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: hiro, Assigned: hiro)

Tracking

unspecified
mozilla55
Points:
---

Firefox Tracking Flags

(firefox55 fixed)

Details

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

(Assignee)

Description

a year ago
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 hidden (mozreview-request)

Comment 2

a year ago
mozreview-review
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
Attachment #8844693 - Flags: review?(boris.chiou) → review+

Comment 3

a year ago
Pushed by hikezoe@mozilla.com:
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

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/03d9643f0fa0
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
status-firefox55: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.