- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Mar 2022 09:41:44 +0000
- To: public-css-archive@w3.org
> Excuse me, but I fail to understand that's the win-win solution because that does not take into account of the opinions of users who consider @if more appropriate. @ianthedev It's win-win as in: CSS Authors get to use the feature and Sass doesn't break. — Everybody wins. Note that the choice that needs to be made here is on the name, not on whether the feature is getting defined or not. It will get defined, but one of the possible two suggested names has the side-effect that it breaks Sass. For break-scenario I see a reasonable upgrade path _([see above](https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1063892265))_ along with some other good suggestions here, but could be that I didn't assess them properly as I'm not entirely familiar with the Sass Ecosystem. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6684#issuecomment-1072241093 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 March 2022 09:41:45 UTC