Closed Bug 1642830 Opened 4 years ago Closed 1 year ago

New wpt failures in /css/css-scroll-snap/input/keyboard.html

Categories

(Core :: Layout: Scrolling and Overflow, defect)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wpt])

Syncing wpt PR 23911 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

/css/css-scroll-snap/input/keyboard.html
If there is no valid snap offset on the arrow key's direction other than the current offset, and the scroll-snap-type is proximity, go to the original intended offset: FAIL (Chrome: PASS)
If the original intended offset is valid as making a snap area cover the snapport, but there's a defined snap offset in between, use the defined snap offset.: FAIL (Chrome: PASS)
Snaps to top-left after pressing ArrowUp: FAIL (Chrome: PASS)
Snaps to top-left after pressing ArrowLeft: FAIL (Chrome: PASS)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

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

Severity: -- → S3
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.