Closed Bug 1827912 Opened 2 years ago Closed 2 years ago

test_driver.Actions.scroll doesn't work with origin: element

Categories

(Core :: DOM: Core & HTML, enhancement)

Firefox 114
enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: awogbemila, Unassigned)

Details

Steps to reproduce:

(Apologies if this is not the right channel for this issue, happy to be advised on a more appropriate channel :))

View wpt.fyi[1] test results and set the "Show Details" toggle button. You will see that for firefox the WPT is failing with the error "ValueError: Unrecognised web element".

Alternatively, you can manually run the wpt against firefox by setting up the wpt following the instructions on the WPT Github repo[2] and then running ./wpt run firefox dom/events/scrolling/scrollend-event-not-fired-on-no-scroll.html (requires firefox to be in PATH). It will produce the same error.

It seems to be happening because the test uses test_driver.Actions().scroll(..., {origin:element}) as is described in web-platform-test.org[3]. I've played around with using the default {origin:"viewport"} which seems to work fine so this is perhaps an issue with geckodriver's handling of the API.

[1] https://wpt.fyi/results/dom/events/scrolling/scrollend-event-not-fired-on-no-scroll.html?label=master&label=experimental&aligned&q=scrollend
[2] https://github.com/web-platform-tests/wpt#setting-up-the-repo
[3] https://web-platform-tests.org/writing-tests/testdriver.html#Actions.scroll

Actual results:

The test fails with "ValueError: Unrecognised web element" error.

Expected results:

The reported error should not occur.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core

I think this issue should have been addressed with this commit: https://github.com/mozilla/gecko-dev/commit/c033a12a53bb42d4b0de3944b132ab5c787b0424 but it seems that an older version of the marionette driver is what gets downloaded when I try to run this locally. The same thing could possibly be happening with the wpt.fyi runs.

The issue does not seem to be present in the wpt.fyi runs anymore. The test mentioned in comment 1 is now failing for other reasons.. Closing this.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.