Re: [csswg-drafts] [css-cascade-6] Do we need 'sibling' scopes in @scope? (#8299)

This selector workaround also fails in situations where there are no `.lower` elements to end the scope. Instead of selecting everything in the scope, it selects nothing. There are similar selectors that roughly approximate vertical scopes, with very similar limitations. They work sometimes, but they aren't reliable in large component-driven projects, because you don't know when those edge cases might come up. 

But the existence of selectors that get close isn't really the driving question here. Many new features improve on existing patterns. I'm more interested in the use-cases that would drive an author to even consider the selector pattern. Is this form of sibling-scoped selection something that authors need or want? What are example problems that it solves?

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


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

Received on Thursday, 12 January 2023 17:20:36 UTC