Closed
Bug 1325308
Opened 7 years ago
Closed 7 years ago
Test for "a single keyframe sequence with string offset" has the wrong computedOffset
Categories
(Core :: DOM: Animation, defect, P3)
Core
DOM: Animation
Tracking
()
RESOLVED
FIXED
mozilla53
| Tracking | Status | |
|---|---|---|
| firefox53 | --- | fixed |
People
(Reporter: birtles, Assigned: birtles)
Details
Attachments
(2 files)
This test case, added when merging Blink tests[1] expects an offset of '0.5' to produce an offset of 0.5 and a computedOffset of 1. That's clearly wrong. [1] https://github.com/w3c/web-platform-tests/commit/e656c20e538a83efe94fdd26c3e5eb056b148c5f#diff-54ba468151a7d5a883fe7a9be379564c
| Comment hidden (mozreview-request) |
| Comment hidden (mozreview-request) |
|
Assignee | |
Updated•7 years ago
|
Attachment #8821051 -
Flags: review?(hiikezoe)
Attachment #8821052 -
Flags: review?(hiikezoe)
|
||
Comment 3•7 years ago
|
||
| mozreview-review | ||
Comment on attachment 8821051 [details] Bug 1325308 - Fix expected computedOffset for 'a single keyframe sequence with string offset' test https://reviewboard.mozilla.org/r/100432/#review100962
Attachment #8821051 -
Flags: review?(hiikezoe) → review+
|
|
||
Comment 4•7 years ago
|
||
| mozreview-review | ||
Comment on attachment 8821052 [details] Bug 1325308 - Convert non-promise test to use regular test() function https://reviewboard.mozilla.org/r/100434/#review100966
Attachment #8821052 -
Flags: review?(hiikezoe) → review+
Pushed by bbirtles@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9f37791a9a92 Fix expected computedOffset for 'a single keyframe sequence with string offset' test r=hiro https://hg.mozilla.org/integration/autoland/rev/c09596126766 Convert non-promise test to use regular test() function r=hiro
|
||
Comment 6•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/9f37791a9a92 https://hg.mozilla.org/mozilla-central/rev/c09596126766
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in
before you can comment on or make changes to this bug.
Description
•