- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 May 2016 10:30:06 +0000
- To: public-css-archive@w3.org
I'd prefer `@if`... not very strongly, though. I agree with @Marat-Tanalin that we should not pick a weird syntax just to avoid conflicting with a preprocessor, and preprocessors can always work around that easily, either via a breaking change stated in the release note or introducing a new keyword. I can imagine that if we choose `@when` and `@else-when`, more developers would tend to critize that CSSWG is making their life harder via adding some syntax different than what they are familiar with, rather than appreciating the work of avoiding the imaginary breakage. I think the criteria is, is there more web developers use SASS's `@if` than those who do not use SASS's `@if` (or do not use SASS at all) but familiar with the general if-else structure? What's the percentage? -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/112#issuecomment-221835505 using your GitHub account
Received on Thursday, 26 May 2016 10:30:08 UTC