Closed
Bug 1886314
Opened 6 months ago
Closed 3 days ago
New wpt failures in /css/css-cascade/scope-evaluation.html
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
DUPLICATE
of bug 1886441
People
(Reporter: wpt-sync, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [wpt])
Syncing wpt PR 45206 found new untriaged test failures in CI
Tests Affected
Firefox-only failures
- /css/css-cascade/scope-evaluation.html [wpt.fyi]
- Single scope:
FAIL
- Selecting self with :scope:
FAIL
- Single scope with limit:
FAIL
- Single scope, :scope pseudo in main selector:
FAIL
- Single scope, :scope pseudo in to-selector:
FAIL
- Multiple scopes, :scope pseudo in to-selector:
FAIL
- Inner @scope with :scope in from-selector:
FAIL
- Multiple scopes from same @scope-rule, only one limited:
FAIL
- Nested scopes:
FAIL
- Nested scopes, with to-selector:
FAIL
- :scope selecting itself:
FAIL
- The scoping limit is not in scope:
FAIL
- Simulated inclusive scoping limit:
FAIL
- Relative selector inside @scope:
FAIL
- Scope root with :has():
FAIL
- Single scope:
New Tests That Don't Pass
- /css/css-cascade/scope-evaluation.html [wpt.fyi]
- Any scope limit makes the element out of scope:
FAIL
(Chrome:PASS
, Safari:FAIL
)
- Any scope limit makes the element out of scope:
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1886282 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.
You need to log in
before you can comment on or make changes to this bug.
Description
•