New wpt failures in /css/css-contain/container-queries/custom-property-style-queries.html
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
People
(Reporter: wpt-sync, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [wpt])
Syncing wpt PR 45759 found new untriaged test failures in CI
Tests Affected
Firefox-only failures
- /css/css-contain/container-queries/custom-property-style-queries.html [wpt.fyi]
- Style query 'space' matching:
FAIL
- Style query 'space' not matching:
FAIL
- Style query 'space' matching:
New Tests That Don't Pass
- /css/css-contain/container-queries/custom-property-style-queries.html [wpt.fyi]
- Style query 'initial' matching (with explicit 'initial' value):
FAIL
(Chrome:PASS
, Safari:FAIL
) - Style query matching negated value-less query against initial value (with explicit 'initial' value):
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Style query 'initial' matching (with explicit 'initial' value):
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1891940 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•7 months ago
|
Updated•7 months ago
|
Updated•6 months ago
|
Comment 2•6 months ago
|
||
The severity field for this bug is set to S4
. However, the following bug duplicate has higher severity:
- Bug 1881854: S3
:emilio, could you consider increasing the severity of this bug to S3
?
For more information, please visit BugBot documentation.
Comment 3•6 months ago
|
||
Oops, severity increased to S3. :)
Description
•