Re: [csswg-drafts] [css-nesting-1] Name, terminology, and nesting selector misnomers are footguns (solution proposed) (#8329)

After some further reading, I see the scoping concept is being updated as part of [css-cascade-6](https://drafts.csswg.org/css-cascade-6/#scoped-stylesl), and even has issue 11 for determining the interaction with css-nesting-1.

Based on the direction of that, I more strongly believe "nesting" is not a useful term for the unique behaviour of this spec, especially when multiple at-rule blocks already allow nesting that will likely intermix with this one.

The newer expanded use of `:scope` with scoping-limits also seem to fit this concept and purpose better, and it shouldn't conflict unless there is a practical use-case (is there?) for needing to refer to an earlier `:scope` in a case where `@scope` and `@nest` might be nested inside one another (is this already considered for `@scope` nesting? I'd lean more towards having a `:parent-scope(1)` or `:scope(-1)` for such a purpose though). I can't see any special cases where `:scope` and `&` couldn't be used interchangeably as it stands (but of course I may have missed many things).

-- 
GitHub Notification of comment by zealvurte
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8329#issuecomment-1397713977 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 19 January 2023 22:51:37 UTC