- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2023 17:52:29 +0000
- To: public-css-archive@w3.org
+1 to Tab's `@nest` proposal. > before we decide to add even more syntax to CSS to do similar but slightly different things (which is an antipattern from a UX/DX perspective). Isn't special-casing `&` just a different (worse) way to add more stuff that does slightly different things? :-) > Far better to say that the specificity is equal to the first one that actually matches, rather than the max specificity in the list! No, please keep the specificity calculation _simple_, and avoid any kind of "dynamic" specificity based on context. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9492#issuecomment-1779773461 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 October 2023 17:52:31 UTC