Re: [csswg-drafts] [css-cascade-6] Strong vs weak scoping proximity (#6790)

I'd go for something like `@scope strong (upper-element) to (lower-element) { /* ... */ }` but otherwise I agree that adding a mechanism for strong scoping later on would be the best way forward.

That way `@scope` can get shipped and people start playing around with it and if enough of a need for strong scoping appears down the line, it can just be added later on (and if all the use-cases can get solved otherwise, then that's fine too).

To be honest, I think that's been the general consensus for a while now. It might be time to just conclude that the default will be weak scoping and move on with getting this into the browsers.

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


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

Received on Thursday, 16 March 2023 08:18:21 UTC