Open Bug 2006585 Opened 7 days ago Updated 1 day ago

[wpt-sync] Sync PR 56804 - Avoid timeout in scroll animation test

Categories

(Core :: Layout, task, P4)

Product:
Core
Component:
Layout
Type:
task

Tracking

()

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Callum Law <callumlaw1709@outlook.com> wrote:

Avoid timeout in scroll animation test

As with the test above we are required to wait for two animation frames to pass, this is because the onfinish callback is executing within step 3 of the update animations and send events procedure: "perform a microtask checkpoint" and thus the callback passed to the first requestAnimationFrame will execute within the same iteration of the update the rendering procedure (i.e. before we have a chance to run the update animations and send events procedure with scrollTop set to 0).

Component: web-platform-tests → Layout
Product: Testing → Core

CI Results

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

Total 1 tests and 25 subtests

Status Summary

Firefox

OK : 1
FAIL: 25

Chrome

OK : 1
PASS: 25

Safari

OK : 1
PASS: 25

Links

GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

  • /scroll-animations/scroll-timelines/updating-the-finished-state.html [wpt.fyi]
    • Updating the finished state when seeking past end: FAIL linked bug:Bug 1949826
    • Updating the finished state when playing exactly to end: FAIL linked bug:Bug 1949826
    • Updating the finished state when seeking exactly to end: FAIL linked bug:Bug 1949826
    • Updating the finished state when playing in reverse past zero: FAIL linked bug:Bug 1949826
    • Updating the finished state when seeking a reversed animation past zero: FAIL linked bug:Bug 1949826
    • Updating the finished state when playing a reversed animation exactly to zero: FAIL linked bug:Bug 1949826
    • Updating the finished state when seeking a reversed animation exactly to zero: FAIL linked bug:Bug 1949826
    • Updating the finished state when seeking before end: FAIL linked bug:Bug 1949826
    • Updating the finished state when seeking a reversed animation before end: FAIL linked bug:Bug 1949826
    • Updating the finished state when playback rate is zero and the current time is less than zero: FAIL linked bug:Bug 1949826
    • Updating the finished state when playback rate is zero and the current time is less than end: FAIL linked bug:Bug 1949826
    • Updating the finished state when playback rate is zero and the currenttime is greater than end: FAIL linked bug:Bug 1949826
    • Updating the finished state when current time is unresolved: FAIL linked bug:Bug 1949826
    • Updating the finished state when start time is unresolved and did seek = true: FAIL linked bug:Bug 1949826
    • Finish notification steps don't run when the animation seeks to finish and then seeks back again: FAIL linked bug:Bug 1949826
    • Finish notification steps run when the animation completes normally: FAIL linked bug:Bug 1949826
    • Finish notification steps run when an animation without a target effect completes normally: FAIL linked bug:Bug 1949826
    • Finish notification steps run when the animation seeks past finish: FAIL linked bug:Bug 1949826
    • Finish notification steps run when the animation completes with .finish(), even if we then seek away: FAIL linked bug:Bug 1949826
    • Animation finished promise is replaced after seeking back to start: FAIL linked bug:Bug 1949826
    • Animation finished promise is replaced after replaying from start: FAIL linked bug:Bug 1949826
    • Animation finish event is fired again after seeking back to start: FAIL linked bug:Bug 1949826
    • Animation finish event is fired again after replaying from start: FAIL
    • finish event is not fired at the end of the active interval when the endDelay has not expired: FAIL linked bug:Bug 1949826
    • finish event is fired after the endDelay has expired: FAIL linked bug:Bug 1949826

New Tests That Don't Pass

  • /scroll-animations/scroll-timelines/updating-the-finished-state.html [wpt.fyi]
    • Updating the finished state when seeking past end: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when playing exactly to end: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when seeking exactly to end: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when playing in reverse past zero: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when seeking a reversed animation past zero: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when playing a reversed animation exactly to zero: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when seeking a reversed animation exactly to zero: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when seeking before end: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when seeking a reversed animation before end: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when playback rate is zero and the current time is less than zero: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when playback rate is zero and the current time is less than end: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when playback rate is zero and the currenttime is greater than end: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when current time is unresolved: FAIL (Chrome: PASS, Safari: PASS)
    • Updating the finished state when start time is unresolved and did seek = true: FAIL (Chrome: PASS, Safari: PASS)
    • Finish notification steps don't run when the animation seeks to finish and then seeks back again: FAIL (Chrome: PASS, Safari: PASS)
    • Finish notification steps run when the animation completes normally: FAIL (Chrome: PASS, Safari: PASS)
    • Finish notification steps run when an animation without a target effect completes normally: FAIL (Chrome: PASS, Safari: PASS)
    • Finish notification steps run when the animation seeks past finish: FAIL (Chrome: PASS, Safari: PASS)
    • Finish notification steps run when the animation completes with .finish(), even if we then seek away: FAIL (Chrome: PASS, Safari: PASS)
    • Animation finished promise is replaced after seeking back to start: FAIL (Chrome: PASS, Safari: PASS)
    • Animation finished promise is replaced after replaying from start: FAIL (Chrome: PASS, Safari: PASS)
    • Animation finish event is fired again after seeking back to start: FAIL (Chrome: PASS, Safari: PASS)
    • Animation finish event is fired again after replaying from start: FAIL (Chrome: PASS, Safari: PASS)
    • finish event is not fired at the end of the active interval when the endDelay has not expired: FAIL (Chrome: PASS, Safari: PASS)
    • finish event is fired after the endDelay has expired: FAIL (Chrome: PASS, Safari: PASS)
You need to log in before you can comment on or make changes to this bug.