New wpt failures in /css/selectors/invalidation/input-pseudo-classes-in-has.html
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
People
(Reporter: wpt-sync, Unassigned)
References
Details
(Whiteboard: [wpt])
Syncing wpt PR 33528 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
/css/selectors/invalidation/input-pseudo-classes-in-has.html
:checked & :indeterminate invalidation: FAIL (Chrome: PASS, Safari: FAIL)
:disabled invalidation: FAIL (Chrome: PASS, Safari: FAIL)
:read-only invalidation: FAIL (Chrome: PASS, Safari: FAIL)
:valid invalidation: FAIL (Chrome: PASS, Safari: FAIL)
:default invalidation with input[type=radio]: FAIL (Chrome: PASS, Safari: FAIL)
:required invalidation: FAIL (Chrome: PASS, Safari: FAIL)
:out-of-range invalidation: FAIL (Chrome: PASS, Safari: FAIL)
:placeholder-shown invalidation: FAIL (Chrome: PASS, Safari: FAIL)
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1763324 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.
|
||
Comment 1•3 years ago
|
||
wpt.fyi link: https://wpt.fyi/results/css/selectors/invalidation/input-pseudo-classes-in-has.html
wpt.live link: https://wpt.live/css/selectors/invalidation/input-pseudo-classes-in-has.html
This testcase uses the following styles:
<style>
.ancestor:has(#checkme:checked) { color: green }
.ancestor:has(#checkme:indeterminate) { color: yellowgreen }
.ancestor:has(#checkme:disabled) { color: blue }
.ancestor:has(#textinput:read-only) { color: skyblue }
.ancestor:has(#textinput:placeholder-shown) { color: navy }
.ancestor:has(#radioinput:default) { color: lightblue }
.ancestor:has(#textinput:valid) { color: lightgreen }
.ancestor:has(#numberinput:out-of-range) { color: darkgreen }
.ancestor:has(#numberinput:required) { color: pink }
.ancestor:has(#progress:indeterminate) { color: orange }
Based on that and the has in the test's filename, I think it's trying to test the CSS :has feature, and we're failing most of the test since we don't support that. That's bug 418039.
Description
•