Re: [csswg-drafts] [css-cascade] Opt-in strong proximity for @scope (#8601)

Different two-tier system :)

With `!important` authors get stuck with `why isn't my declaration being applied?`
Once you notice that someone at a distance used `!important` you are forced to also add `!important` (specificity still applies). This escalates until you end up with `!important` everywhere.

The same would be true with `@scope`.
Any mode toggle that makes something have more weight will force others to also add more weight to override the thing that you gave more weight.

How you add more weight is a factor, but it is not the core issue.
It is that you have to add weight because someone else (at a distance) added weight.

> you can always create a new, inner strong `@scope` that further overrides the rules of the (now) middle scope

Exactly.
It forces others to also use a strong `@scope`.
A weak `@scope` would no longer work.

-- 
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8601#issuecomment-1471827398 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 12:01:49 UTC