- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Oct 2023 13:19:27 +0000
- To: public-css-archive@w3.org
@tabatkins If preprocessor users haven’t really stumbled on this in the first place, compatibility with preprocessors is not a benefit, minor or otherwise. It's only a benefit when it's compatible with behaviors they have, actually, experienced. Adding something to CSS is a much wider deployment than adding it to a preprocessor, so “people haven't hit this problem before” should not be an excuse for weird behavior. If you read through the thread and the various polls, there is a very strong signal from developers that the current behavior is confusing. Even worse, for the few that don't find it confusing, it’s due to a broken mental model about the cascade: they thought that `@media` *adds* specificity. So I’m quite worried not just about the ergonomics of this, but also what it teaches authors about the rest of CSS. And it's not like there's an actual implementation reason for the confusing behavior, right? It seems we all agree (?) that changing it produces better ergonomics. So what's the argument for keeping it? Compatibility with Sass and co? We literally have a TAG principle about this exact thing: [2.12 Prioritize usability over compatibility with third-party tools](https://w3ctag.github.io/design-principles/#third-party-tools). -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1766404322 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 October 2023 13:19:29 UTC