CSS Cascading and Inheritance Level 6 (@scope)

[andruud]

Request for position on an emerging web specification

• WebKittens who can provide input: @anttijk

Information about the spec

• Spec Title: CSS Cascading and Inheritance Level 6 (@scope)
• Spec URL: https://drafts.csswg.org/css-cascade-6/#scope-atrule
• GitHub repository: https://github.com/w3c/csswg-drafts/labels/css-cascade-6
• Explainer (if not README.md in the repository): https://css.oddbird.net/scope/explainer/

Design reviews and vendor positions

• TAG Design Review: Early design review of light-DOM CSS Scope proposal w3ctag/design-reviews#593
• Mozilla standards-positions issue: @scope mozilla/standards-positions#625

Bugs tracking this feature

• WebKit Bugzilla:
• Radar:

Anything else we need to know

This RFP covers the @scope rule only, not the new combinator nor the new notation.

[hober]

cc @jensimmons

[jensimmons]

This will be incredibly useful for web developers, especially those creating "components" and delivering those components using some kind of JS framework.

Often such solutions organize the CSS for each component in separate files, and load those files in random order — making it impossible to rely on the cascade for sorting out which rules are applied. @scope would allow developers on such projects to scope their CSS to each component.

Scope is also part of a larger effort to modernize the CSS Cascade — an effort that includes Cascade Layers, Nesting, and Container Queries. Together, these tools will radically change how tech leads architect CSS to meet the demands of today's large-team, multi-year projects. Developers need all four.

[annevk]

Given @jensimmons's comment I suggest we mark this as support seven days from now.

[bramus]

@annevk Do you have an updated on this? It’s been past 7 days since you replied “I suggest we mark this as support seven days from now.”, which would mean that the label position: support can be added? Or are there any blockers/concerns that should be discussed (within the CSSWG, maybe)?

If support is expressed, is it for only the @scope part (as per OP’s FRP) or does it also included support for the scoped descendant combinator and the selector notation?

[annevk]

Thanks for the reminder! The scope of each standards-positions issue is determined by OP.

[bramus]

Perfect, thank you.

[hober]

Closing as we've identified our position.