- From: Michael Mifsud via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 May 2016 11:22:10 +0000
- To: public-css-archive@w3.org
>The original Sass file before preprocessing is not processed directly by browsers. True, but it leaves the author unable to use the CSS `@if` syntax. > new keyword like `@css-if` which is converted to the CSS's `@if` Also true. This shifts the burden off from the existing ecosystem and onto the everyday developers. *** Aside from technology I think there are real concerns regarding the effects on the wider CSS and Sass communities, some potential examples: _Raising the barrier to entry_ by negatively affecting google search results for the correct syntax for a given context i.e. authoring in CSS or Sass. _Causing confusion_ where-in blog authors would need to explicitly declare CSS `@if` or Sass `@if` in their content. -- GitHub Notification of comment by xzyfer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/112#issuecomment-221845009 using your GitHub account
Received on Thursday, 26 May 2016 11:22:12 UTC