-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS Cascading and Inheritance Level 6 (@scope) #13
Comments
cc @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 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. |
Given @jensimmons's comment I suggest we mark this as support seven days from now. |
@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 |
Thanks for the reminder! The scope of each standards-positions issue is determined by OP. |
Perfect, thank you. |
Closing as we've identified our position. |
Request for position on an emerging web specification
Information about the spec
@scope
)Design reviews and vendor positions
Bugs tracking this feature
Anything else we need to know
This RFP covers the @scope rule only, not the new combinator nor the new notation.
The text was updated successfully, but these errors were encountered: