Add support for @scope
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
People
(Reporter: sebo, Unassigned)
References
(Depends on 6 open bugs, Blocks 4 open bugs, )
Details
(Keywords: dev-doc-needed, parity-chrome, parity-safari)
The CSS Cascading and Inheritance Module Level 6 introduces an @scope
rule that restricts any rules inside it to a subtree or fragment of a document.
This bug is meant to track the implementation of this at-rule.
Sebastian
Comment 1•11 months ago
|
||
For context, Chrome is planning to ship this in M118 (~October) and it is soon to be enabled by default in Canary. Their intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/OEfGbd74QnQ/m/KaX-2hhRAAAJ
Comment 2•7 months ago
|
||
Safari has also shipped this in the latest Tech Preview: https://developer.apple.com/documentation/safari-technology-preview-release-notes/stp-release-185
Updated•7 months ago
|
Comment 3•7 months ago
•
|
||
In the radar for H1 2024 via https://mozilla-hub.atlassian.net/browse/FFXP-1523
Updated•6 months ago
|
Comment 4•5 months ago
|
||
RE interop-2024-starting-style relationship: that's [at least] for this test, which uses @scope and is part of that interop-2024 focus area:
https://wpt.fyi/results/css/css-cascade/scope-starting-style.html
http://wpt.live/css/css-cascade/scope-starting-style.html
Comment 5•5 months ago
|
||
We should probably exclude those from interop then, fwiw.
Comment 6•5 months ago
|
||
Makes sense. I filed https://github.com/web-platform-tests/interop/issues/641 to remove that test.
(I think it's just the one test that uses @scope.)
Updated•5 months ago
|
Reporter | ||
Comment 8•3 months ago
|
||
For reference, the intent to prototype @scope
was posted at https://groups.google.com/a/mozilla.org/g/dev-platform/c/VokGNgqFqt0.
Sebastian
Description
•