1938118 - New wpt failures in /css/css-overflow/ [column-scroll-marker-008.html, column-scroll-marker-reattach-target-current.html, scroll-marker-001.html, and 36 others]

Status: NEW

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

Description

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

Syncing wpt PR 49729 found new untriaged test failures in CI

Tests Affected

Firefox-only failures

• /css/css-overflow/scroll-buttons-selection.html [wpt.fyi]
  • CSS Test: ::scroll-marker click with active selection: FAIL

New Tests That Don't Pass

• /css/css-overflow/column-scroll-marker-008.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/column-scroll-marker-reattach-target-current.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-001.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-002.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-003.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-004.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-005.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-006.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-007.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-008.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-009.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-010.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-011.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-012.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-counters.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-dynamic.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-001.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-002.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-005.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-007.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-008.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-009.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-011.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-013.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-015.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-add-dynamic-001.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-add-dynamic-002.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-add-dynamic-003.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-add-dynamic-004.html [wpt.fyi]: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-013.html [wpt.fyi]
  • Scroll last item into view: FAIL (Chrome: PASS, Safari: FAIL)
  • Scroll seventh item into view: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-activation-retains-focus.html [wpt.fyi]
  • CSS Test: ::scroll-marker retains focus on ::scroll-marker: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-controls-scroll-tracking-001.html [wpt.fyi]
  • ::scroll-marker is not activated when its originating element is not scrolled into the view: FAIL (Chrome: PASS, Safari: FAIL)
  • ::scroll-marker is activated when its originating element is scrolled into the view: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-controls-scroll-tracking-002.html [wpt.fyi]
  • ::scroll-marker is not active when its originating element is not scrolled into the view: FAIL (Chrome: PASS, Safari: FAIL)
  • ::scroll-marker is active when its originating element is scrolled into the view: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-controls-scroll-tracking-003.html [wpt.fyi]
  • ::scroll-marker is not activated when its originating element is not scrolled into the view: FAIL (Chrome: PASS, Safari: FAIL)
  • ::scroll-marker is activated when its originating element is scrolled into the view: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-003.html [wpt.fyi]
  • ::scroll-marker-group empty: FAIL (Chrome: PASS, Safari: FAIL)
  • ::scroll-marker-group with red background: FAIL (Chrome: PASS, Safari: FAIL)
  • ::scroll-marker-group empty again: FAIL (Chrome: PASS, Safari: FAIL)
  • ::scroll-marker-group with red background again: FAIL (Chrome: PASS, Safari: FAIL)
  • ::scroll-marker-group with green background: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-012.html [wpt.fyi]
  • Click on third scroll marker: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-marker-group-014.html [wpt.fyi]
  • Click on third scroll marker: FAIL (Chrome: PASS, Safari: FAIL)
• /css/css-overflow/scroll-markers-focus-active-element.html [wpt.fyi]
  • CSS Test: document.activeElement for ::scroll-marker is scroller: FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

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