W3C home > Mailing lists > Public > www-style@w3.org > May 2012

Re: [css-variables] Using $foo as the syntax for variables

From: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
Date: Wed, 23 May 2012 02:23:33 +0400
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: Brad Kemper <brad.kemper@gmail.com>,Tab Atkins Jr. <jackalmage@gmail.com>,www-style list <www-style@w3.org>
Message-Id: <895501337725413@web11f.yandex.ru>
BTW, I believe most of real-world websites does not use SASS at all and use regular standard stylesheets instead. So CSS/SASS interoperability should not be an important blocker for CSS to get better.

If something should be changed, it's SASS based on CSS choices, not CSS based on SASS choices (moreover, as far as I can recall, something like this has been stated by SASS author himself here in www-style list before).


22.05.2012, 23:22, "Sylvain Galineau" <sylvaing@microsoft.com>:
> [Brad Kemper:]
>
>> šI think this would cause trouble to people who use SASS, but still want
>> šsome variable use in their final, rendered CSS. Also, I don't like the
>> šidea of a completely different pattern (functional notation) for similar
>> šuse combined with a second argument, such as default.
>
> I have been concerned about this as well; not only might it cause some code
> maintenance confusion but the assumption seems to be that the two shall never
> meet in the same stylesheet. Though, for now, I am lacking the imagination to
> think of the awesome one could do by generating CSS variable constructs with
> SASS on the server, I'm not sure we can make this assumption. Or that it is
> desirable to make using the two together more difficult. We simply have no
> control on whether and when SASS will go away. We do have control on how
> easy/hard it would be to use variables and frameworks such as SASS together
> though.
Received on Tuesday, 22 May 2012 22:24:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:54 GMT