- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Mar 2023 16:02:40 +0000
- To: public-css-archive@w3.org
My intuition is also to not add the specificity of the scope rule. I think our goal with scoping and layers should be to give authors tools *other than specificity* to control the cascade, so including it here doesn't help. (Specificity is a heuristic. It works well in a lot of cases, and that's why we have it, but it's still a heuristic. It would be better if authors had better tools for explicit control over the cascade, imho.) -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8500#issuecomment-1450399580 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 16:02:42 UTC