Closed Bug 1600764 Opened 5 years ago Closed 4 years ago

[wpt-sync] Sync PR 20567 - Removed exception for setting current time on a scroll linked animation

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox73 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla73
Tracking Flags:
Tracking Status
firefox73 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 20567 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/20567
Details from upstream follow.

Jordan Taylor <jortaylo@microsoft.com> wrote:

Removed exception for setting current time on a scroll linked animation

As far as I can tell, we are now ok to remove the exception that was
preventing current time from being set on animations using a
ScrollTimeline.

Added test for setting current time on scroll linked animation

Bug: 916117
Change-Id: I8017ce2f81496057cf5e4b8bb16b14707ee82484
Reviewed-on: https://chromium-review.googlesource.com/1945923
WPT-Export-Revision: 79213ec13018c4351df531ac7986cdddac760779

CI Results

Ran 13 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 3 subtests

Status Summary

Firefox

OK : 2
FAIL: 11

Chrome

OK : 2
PASS: 1
FAIL: 10

Safari

OK : 2
FAIL: 11

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/scroll-animations/setting-current-time.html
Set animation current time to a value beyond effect end.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a negative value.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value while playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation current time to null throws TypeError.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation.currentTime then restarting the animation should reset the current time.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value without playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting current time while play pending overrides the current time: FAIL (Chrome: FAIL, Safari: FAIL)
Set Animation current time then scroll.: FAIL (Chrome: FAIL, Safari: FAIL)
/scroll-animations/scroll-animation.html
Animation start and current times are correct for each animation state when the animation starts playing with advanced scroller.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct when multiple animations are attached to the same timeline.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct for each animation state.: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Ran 13 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 3 subtests

Status Summary

Firefox

OK : 2
FAIL: 11

Chrome

OK : 2
PASS: 1
FAIL: 10

Safari

OK : 2
FAIL: 11

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/scroll-animations/setting-current-time.html
Set animation current time to a value beyond effect end.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a negative value.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value while playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation current time to null throws TypeError.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation.currentTime then restarting the animation should reset the current time.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value without playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting current time while play pending overrides the current time: FAIL (Chrome: FAIL, Safari: FAIL)
Set Animation current time then scroll.: FAIL (Chrome: FAIL, Safari: FAIL)
/scroll-animations/scroll-animation.html
Animation start and current times are correct for each animation state when the animation starts playing with advanced scroller.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct when multiple animations are attached to the same timeline.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct for each animation state.: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Ran 13 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 3 subtests

Status Summary

Firefox

OK : 2
FAIL: 11

Chrome

OK : 2
PASS: 1
FAIL: 10

Safari

OK : 2
FAIL: 11

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/scroll-animations/setting-current-time.html
Set animation current time to a value beyond effect end.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a negative value.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value while playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation current time to null throws TypeError.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation.currentTime then restarting the animation should reset the current time.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value without playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting current time while play pending overrides the current time: FAIL (Chrome: FAIL, Safari: FAIL)
Set Animation current time then scroll.: FAIL (Chrome: FAIL, Safari: FAIL)
/scroll-animations/scroll-animation.html
Animation start and current times are correct for each animation state when the animation starts playing with advanced scroller.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct when multiple animations are attached to the same timeline.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct for each animation state.: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4ac47464c832
[wpt PR 20567] - Removed exception for setting current time on a scroll linked animation, a=testonly
https://hg.mozilla.org/integration/autoland/rev/3e9ad9d7cd95
[wpt PR 20567] - Update wpt metadata, a=testonly

CI Results

Ran 13 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 3 subtests

Status Summary

Firefox

OK : 2
FAIL: 11

Chrome

OK : 2
PASS: 1
FAIL: 10

Safari

OK : 2
FAIL: 11

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/scroll-animations/setting-current-time.html
Set animation current time to a value beyond effect end.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a negative value.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value while playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation current time to null throws TypeError.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting animation.currentTime then restarting the animation should reset the current time.: FAIL (Chrome: FAIL, Safari: FAIL)
Set animation current time to a valid value without playing.: FAIL (Chrome: FAIL, Safari: FAIL)
Setting current time while play pending overrides the current time: FAIL (Chrome: FAIL, Safari: FAIL)
Set Animation current time then scroll.: FAIL (Chrome: FAIL, Safari: FAIL)
/scroll-animations/scroll-animation.html
Animation start and current times are correct for each animation state when the animation starts playing with advanced scroller.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct when multiple animations are attached to the same timeline.: FAIL (Chrome: FAIL, Safari: FAIL)
Animation start and current times are correct for each animation state.: FAIL (Chrome: PASS, Safari: FAIL)

Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/4ac47464c832
https://hg.mozilla.org/mozilla-central/rev/3e9ad9d7cd95

Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox73: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in before you can comment on or make changes to this bug.