Open Bug 1830512 (@scope) Opened 1 year ago Updated 5 days ago

Add support for @scope


(Core :: CSS Parsing and Computation, enhancement)





(Reporter: sebo, Unassigned)


(Depends on 6 open bugs, Blocks 4 open bugs, )


(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.


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:

Depends on: 1882379
Depends on: 1882581

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:

We should probably exclude those from interop then, fwiw.

Makes sense. I filed to remove that test.

(I think it's just the one test that uses @scope.)

Duplicate of this bug: 1542645
Depends on: 1883101
Depends on: 1886441
Depends on: 1889109
Depends on: 1890809

For reference, the intent to prototype @scope was posted at


Depends on: 1903533
No longer depends on: 1903533
Depends on: 1908279
You need to log in before you can comment on or make changes to this bug.