- From: Keith Grant via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Mar 2023 20:03:21 +0000
- To: public-css-archive@w3.org
On a higher level, maybe the question is this: is `@scope` intended to give developers more control over targeting elements, or is it meant to take away the specificity foot-gun (almost) entirely? If the goal is to make it so we never have to worry about specificity doing "unexpected" things then strong scoping makes sense; but if the goal is to provide developers with a multiple levers to pull (layer, scope, specificity) and let them devise their own systems for managing them, weak scoping is almost certainly the more versatile approach. -- GitHub Notification of comment by keithjgrant Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1450775732 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 March 2023 20:03:23 UTC