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

Re: [css-variables] CSS Variables are a NEW kind of variable

From: François REMY <fremycompany_pub@yahoo.fr>
Date: Thu, 14 Jun 2012 13:39:35 +0200
Message-ID: <01B55EC08D5A47C2A15B61812D5478E9@FREMYD2>
To: "Sylvain Galineau" <sylvaing@microsoft.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "Chris Eppstein" <chris@eppsteins.net>
Cc: "Divya Manian" <manian@adobe.com>, <www-style@w3.org>
|
| 1. Give users the extra capability suggested to them by the syntax 
[=referencing the value of framework-provided properties in addition to data 
properties]
|

It should be discussed among implementors to see if it's possible to add 
this quickly to CSS (this is rather similar to 'inherit' so it all depends 
of how browsers handles 'inherit' internally; could browsers modify their 
implementation to allow (partial) inheriting from other properties?). If it 
is easily done, we should modify the specification to allow it.

However, I'm not understanding at all why it is critical to add this 
capability to the CSS-VARIABLES L1 specification. If we agree this is an use 
case we probably want to cover in the future, and if we have a syntax for it 
that accept it (and we have), I don't see why we can't leave a note in the 
specification saying that "For optimization reasons, CSS-VARIABLES L1 
doesn't allow to reference framework-provided properties. This limitation 
may be lifted in a future iteration of this module."

People are able to grasp "optimization reasons".




|
| 2. Adjust the syntax in such a manner that 'universal' property references 
are unambiguously out of scope.
|

The more you get people asking for something, the more people need it. 
Killing a request by making it impossible doesn't solve the problem. Worse, 
it makes it difficult (or impossible) to fix in a next iteration of the 
language. 
Received on Thursday, 14 June 2012 11:40:12 GMT

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