Open
Bug 1945196
Opened 23 days ago
Updated 4 days ago
New wpt failures in /css/css-overflow/ [scroll-marker-selection-picks-closest.html, scroll-markers-updated-by-programmatic-scroll.html]
Categories
(Core :: Layout: Scrolling and Overflow, defect, P3)
Core
Layout: Scrolling and Overflow
Tracking
()
NEW
People
(Reporter: wpt-sync, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [wpt])
Syncing wpt PR 50410 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
- /css/css-overflow/scroll-marker-selection-picks-closest.html [wpt.fyi]
- scroll-marker 0 selected at scrollLeft = 0:
FAIL
(Chrome:PASS
, Safari:FAIL
) - scroll-marker 0 selected just before mid point of item0:
FAIL
(Chrome:PASS
, Safari:TIMEOUT
) - scroll-marker 1 selected just after mid point of item0:
FAIL
(Chrome:PASS
, Safari:NOTRUN
) - scroll-marker 1 selected at left edge of item1:
FAIL
(Chrome:PASS
, Safari:NOTRUN
) - scroll-marker 1 selected just before mid point of item1:
FAIL
(Chrome:PASS
, Safari:NOTRUN
) - scroll-marker 2 selected just after mid point of item1:
FAIL
(Chrome:PASS
, Safari:NOTRUN
) - scroll-marker 2 selected just at left edge of item2:
FAIL
(Chrome:PASS
, Safari:NOTRUN
)
- scroll-marker 0 selected at scrollLeft = 0:
- /css/css-overflow/scroll-markers-updated-by-programmatic-scroll.html [wpt.fyi]
- The selected ::scroll-marker is updated using the eventual scroll position for a programmatic scroll:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- The selected ::scroll-marker is updated using the eventual scroll position for a programmatic scroll:
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1945162 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.
Updated•4 days ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•