1918806 - New wpt failures in /css/css-overscroll-behavior/overscroll-behavior.html

Status: RESOLVED FIXED

(Core :: Layout, defect, P3)

Description

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

Syncing wpt PR 48163 found new untriaged test failures in CI

Tests Affected

Firefox-only failures

• /css/css-overscroll-behavior/overscroll-behavior.html [wpt.fyi]
  • overscroll-behavior prevents scroll-propagation in the area and direction as specified: FAIL [Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-qr-opt-geckoview, Gecko-linux1804-64-qr-opt, GitHub], PASS [Gecko-linux1804-64-qr-debug, Gecko-windows11-32-2009-qr-debug, Gecko-windows11-32-2009-qr-opt, Gecko-windows11-64-2009-qr-debug, Gecko-windows11-64-2009-qr-opt]

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1918753 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

[Emilio Cobos Álvarez (:emilio)]

Hiro, this seems some scroll snap issue, or some issue with the test change that Blink did above... Mind taking a look?

S3 because it was caused from a test-only change, so unlikely to uncover anything that wasn't around before.

Comment 3

[Emilio Cobos Álvarez (:emilio)]

This change actually caused a lot more regressions, see bug 1918805... So it's probably worth investigatting a little bit more...

Comment 4

[Hiroyuki Ikezoe (:hiro)]

This is because the test in question uses a WebDriver's click action, unfortunately the click event doesn't run through APZ code at all, thus the previous wheel transaction being handled by APZ isn't interrupted by the mouse click. This restriction will not be solved until we finished implementing all events handling in the parent process. CCing Henrik.

With setting dom.event.wheel-event-groups.enabled:true, mousewheel.transaction.timeout:0, the test passes properly. A try run (it's still running though).

Comment 5

[Hiroyuki Ikezoe (:hiro)]

Attachment: Bug 1918806 - Explicitly set `dom.event.wheel-event-groups.enabled:true, mousewheel.transaction.timeout:0` on overscroll-behavior.html. r?botond

Without setting the prefs, any WebDriver's wheel action is treated in a single
wheel transaction because a mouse click event [1] which is supposed to trigger
creating a new wheel transaction is not processed by APZ.

[1] https://searchfox.org/mozilla-central/rev/c169f7d0287c1a6a5dd7469864135e605eed765f/testing/web-platform/tests/css/css-overscroll-behavior/overscroll-behavior.html#194

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/920dd9bc5aeb
Explicitly set `dom.event.wheel-event-groups.enabled:true, mousewheel.transaction.timeout:0` on overscroll-behavior.html. r=botond

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Thank you Hiro. Let me add the bug as dependency for bug 1848958 where I'm going to send mouse events through APZ. So won't forget about that one.

Comment 8

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/920dd9bc5aeb