- From: Jen Simmons via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Oct 2023 21:27:31 +0000
- To: public-css-archive@w3.org
I agree with Lea: > I think the current behavior is extremely unintuitive, and 10 years down the line we will regret opting for consistency with today’s preprocessors over predictable, natural behavior. A desire to match Sass is a terrible reason. (Especially if the only reason Sass & other tools made their choice is that they could not implement the more intuitive behavior.) We should be designing the language for the future — for 20+ years from now, when the majority of developers have never used Sass, and those that did don't remember how it worked. I've not heard any other reason put forth besides: this is how all the tooling does it, and we don't think it's a big deal. I don't hear anyone arguing that this design is good for the cascade, or makes sense, or is something future developers will easily learn. I believe this will be a very confusing problem for developers trying to debug their code if we don't fix it. -- GitHub Notification of comment by jensimmons Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1749670021 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 October 2023 21:27:33 UTC