1826912 - New wpt failures in /dom/events/scrolling/scrollend-event-for-user-scroll.html

Status: NEW

(Core :: Panning and Zooming, defect, P3)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Syncing wpt PR 39405 found new untriaged test failures in CI

Tests Affected

Firefox-only failures

• /dom/events/scrolling/scrollend-event-for-user-scroll.html [wpt.fyi]: ERROR

CI Results

Missing results from treeherder
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1826786 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.

Comment 1

[David Awogbemila]

This test seems to be affected by 3 issues which I describe in https://bugzilla.mozilla.org/show_bug.cgi?id=1655754#c3.

In summary,

• a scroll is not generated by touch events as the test expects.
• test_driver.Actions().scroll(x, y, dx, dy, {origin: element}) doesn't seem to be handled correctly (by geckodriver?), resulting in "ValueError: Unrecognised web element" errors.
• wheel scrolls generate a scroll but not a scrollend event as the test expects.

They seem to all be related to the test/test environment as firefox scrolls and fires scrollend just fine when tested manually.

Hoping to get some interest on this so wpts can better reflect support for this feature as we try to ship scrollend in Chrome, cheers!

Comment 2

[Dan Robertson (:dlrobertson)]

I'll take a look at this. This does not depend on bug 1785102, as scrollend has already shipped.

Comment 3

[Dan Robertson (:dlrobertson)]

I think this is related to the other keydown scrollend bugs (bug 1831580).