- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Jan 2023 17:51:56 +0000
- To: public-css-archive@w3.org
It is not safe to reuse `:scope` as part of nesting. It's a selector that has existed in production for years, and has a defined meaning. Cascade-6 doesn't invent the selector, it only provides new ways to define scopes that the selector can reference. If we want to use `:scope` here, nesting would need to _become_ a scoping mechanism, with all that entails. That's not a rout we want to go down. Scope is a much more narrowly focussed use-case, with more invasive implications. This conversation has come up several times, because there clearly is overlap in use-cases between nesting and scope - but every time it's discussed, we find that they cannot simply be merged. The use-cases overlap, but are not identical. It's important that they work together, but that requires keeping the syntaxes distinct. Nesting is likely to happen in and around scoped rules, and the distinct meanings need to remain clear even when combined. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8329#issuecomment-1400744767 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 January 2023 17:51:58 UTC