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

RE: [css-variables] status ?

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Fri, 25 May 2012 20:50:50 +0000
To: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
CC: Tab Atkins Jr. <jackalmage@gmail.com>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178290A3572F9@TK5EX14MBXC262.redmond.corp.microsoft.com>


> -----Original Message-----
> From: Marat Tanalin | tanalin.com [mailto:mtanalin@yandex.ru]
> Sent: Friday, May 25, 2012 1:27 PM
> To: Sylvain Galineau
> Cc: Tab Atkins Jr.; Daniel Glazman; www-style@w3.org
> Subject: Re: [css-variables] status ?
> 
> Unfortunately, using preprocessors is not always possible. For example, on
> Windows/IIS platform with a custom CGI executable without ability to use
> any script language, it's completely not an option. Also, using
> preprocessor does not provide ability to make CSS more compact (using Gzip
> not always possible, and is problematic under IIS6 and lower in
> particular).

This is off-topic. Compressing stylesheets when gzip is not available or
compensating for the peculiarities of a given HTTP stack is out of scope.

> 
> Moreover, there is nothing _bad_ in having preprocessor features available
> natively. Using preprocessor for feature that can be easily and reasonably
> implemented natively would be unneeded overhead.
> 
This is off-topic. Local 'preprocessing' is out of scope. 
Received on Friday, 25 May 2012 20:51:23 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:15 UTC