Syncing wpt PR 27908 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

/css/css-scroll-snap/input/keyboard.html: TIMEOUT (Chrome: OK, Safari: TIMEOUT)
Snaps to top-right after pressing ArrowRight: NOTRUN (Chrome: PASS, Safari: NOTRUN)
If the original intended offset is valid as making a snap area cover thesnapport, and there's no other snap offset in between, use the originalintended offset: NOTRUN (Chrome: PASS, Safari: NOTRUN)
If there is no valid snap offset on the arrow key's direction other than the current offset, and the scroll-snap-type is mandatory, stay at the current offset.: NOTRUN (Chrome: PASS, Safari: NOTRUN)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

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

I've fixed an issue that some of test cases in keyboard.html often failed (bug 1841721). But still there are still two test case failures.

I've sent a PR to fix the failures in the upsream since the test cases were based on Chrome specific behaviors, thus I'd say it should be reviewed by other browser engine folks (or the CSS WG folks).

The PR has been merged by ntim. Thanks ntim!