Skip to content
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

@scope #183

Closed
andruud opened this issue Oct 5, 2022 · 6 comments
Closed

@scope #183

andruud opened this issue Oct 5, 2022 · 6 comments
Labels
focus-area-proposal Focus Area Proposal

Comments

@andruud
Copy link

andruud commented Oct 5, 2022

Description

This proposal includes the @scope rule, as specified by: https://drafts.csswg.org/css-cascade-6/#scope-atrule

It does not include:

Rationale

It’s on the list of missing features in the State of CSS survey.

https://2021.stateofcss.com/en-US/opinions/#currently_missing_from_css_wins

Specification

https://drafts.csswg.org/css-cascade-6/#scope-atrule

Tests

https://wpt.fyi/results/css/css-cascade/*scope*:

at-scope-parsing.html
scope-deep.html
scope-evaluation.html
scope-invalidation.html
scope-proximity.html
scope-specificity.html

@gsnedders gsnedders added this to the Interop 2023 milestone Oct 5, 2022
@gsnedders gsnedders added the focus-area-proposal Focus Area Proposal label Oct 5, 2022
@foolip foolip removed this from the Interop 2023 milestone Oct 7, 2022
@tbondwilkinson
Copy link

This is the most important feature for CSS infrastructure in Google.

"Even without widespread browser implementations, a solid CSS scoping spec gives the CSS team a target for our polyfills and designs for the next generation of component scoping, allowing us to stay in line with standard CSS rather than needing to reinvent the wheel"

@foolip
Copy link
Member

foolip commented Nov 11, 2022

There were a handful of mentions of scoping in State of CSS 2022, although not enough to make the top list in #248. There were two direct mentions of @scope, and a few others like these:

  • Scoping is a somewhat solved issue, but no real way to handle it in native CSS without plugins.
  • too many solutions for scoping
  • styling of scoped content (overriding)
@gsnedders
Copy link
Member

There were two direct mentions of @scope

Are you just looking at the interoperability_features_freeform, and not the other freeform responses? If you look across all the freeform responses, there's four direct mentions, plus about another 32 mentions of scoping (most of which just say "scope" with no further detail)?

@foolip
Copy link
Member

foolip commented Nov 11, 2022

@gsnedders yes, just the results of that question in what I'm reporting from #248. I haven't vetted the results of the other two questions, and I think #155 is the only case so far where I happened to notice a lot of mentions and called that out.

Going through the results of those two questions systematically would be great, if you or anyone else has time. I might spend time on it next week, but can't promise.

@foolip
Copy link
Member

foolip commented Nov 11, 2022

In the MDN short survey on CSS & HTML, "CSS scoping (@scope at-rule)" was selected by ~16% of survey takers, putting it in the middle third of the 20 options. (There is some uncertainty as with any survey data.)

@nairnandu
Copy link
Contributor

Thank you for proposing @scope for inclusion in Interop 2023.

We wanted to let you know that this proposal was not selected to be part of Interop this year. We had many strong proposals, and could not accept them all. However this should not be taken as a comment on the technology as a whole, and resubmitting a proposal for this feature as part of a future round of Interop would be welcome.

For an overview of our process, see the proposal selection summary. Thank you again for contributing to Interop 2023!

Posted on behalf of the Interop team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
focus-area-proposal Focus Area Proposal
5 participants