- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 19:58:22 +0000
- To: public-css-archive@w3.org
Right. The case where scope `A` wins over scope `B` is also the case where scope `A` is the closer scope root. Which I don't think is confusing. A 'more nested' mechanism would be akin to specificity. Which: - for `@scope` rules, authors can achieve by using the `&` or additional selectors - for `>>` combinators, the additional specificity is in the selector already I don't see any reason to have a specificity-like cascade mechanic based on 'how many scopes were used to get here'. That would over-complicate what scope is about. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8380#issuecomment-1458758527 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 March 2023 19:58:24 UTC