Open
Bug 1937847
Opened 2 months ago
Updated 1 month ago
New wpt failures in /css/css-overflow/parsing/parsing/ [scroll-buttons-valid.html, scroll-markers-computed.html, scroll-markers-valid.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 49727 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
- /css/css-overflow/parsing/parsing/scroll-buttons-valid.html [wpt.fyi]
- "::scroll-button(up)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(down)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(left)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(right)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-start)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-start)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-end)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-end)" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(up):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(down):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(left):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(right):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-start):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-start):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-end):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-end):focus" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(up):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(down):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(left):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(right):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-start):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-start):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-end):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-end):disabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(up):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(down):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(left):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(right):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-start):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-start):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(inline-end):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
) - "::scroll-button(block-end):enabled" should be a valid selector:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- "::scroll-button(up)" should be a valid selector:
- /css/css-overflow/parsing/parsing/scroll-markers-computed.html [wpt.fyi]
- Property scroll-marker-group value 'initial':
FAIL
(Chrome:PASS
, Safari:FAIL
) - Property scroll-marker-group value 'inherit':
FAIL
(Chrome:PASS
, Safari:FAIL
) - Property scroll-marker-group value 'unset':
FAIL
(Chrome:PASS
, Safari:FAIL
) - Property scroll-marker-group value 'revert':
FAIL
(Chrome:PASS
, Safari:FAIL
) - Property scroll-marker-group value 'none':
FAIL
(Chrome:PASS
, Safari:FAIL
) - Property scroll-marker-group value 'before':
FAIL
(Chrome:PASS
, Safari:FAIL
) - Property scroll-marker-group value 'after':
FAIL
(Chrome:PASS
, Safari:FAIL
) - The scroll-marker-group property shows up in CSSStyleDeclaration enumeration:
FAIL
(Chrome:PASS
, Safari:FAIL
) - The scroll-marker-group property shows up in CSSStyleDeclaration.cssText:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Property scroll-marker-group value 'initial':
- /css/css-overflow/parsing/parsing/scroll-markers-valid.html [wpt.fyi]
- e.style['scroll-marker-group'] = "initial" should set the property value:
FAIL
(Chrome:PASS
, Safari:FAIL
) - e.style['scroll-marker-group'] = "inherit" should set the property value:
FAIL
(Chrome:PASS
, Safari:FAIL
) - e.style['scroll-marker-group'] = "unset" should set the property value:
FAIL
(Chrome:PASS
, Safari:FAIL
) - e.style['scroll-marker-group'] = "revert" should set the property value:
FAIL
(Chrome:PASS
, Safari:FAIL
) - e.style['scroll-marker-group'] = "none" should set the property value:
FAIL
(Chrome:PASS
, Safari:FAIL
) - e.style['scroll-marker-group'] = "before" should set the property value:
FAIL
(Chrome:PASS
, Safari:FAIL
) - e.style['scroll-marker-group'] = "after" should set the property value:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- e.style['scroll-marker-group'] = "initial" should set the property value:
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1937816 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•1 month ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•