- From: Andrew Fedoniouk <news@terrainformatica.com>
- Date: Mon, 06 Oct 2008 16:16:00 -0700
- To: Garrett Smith <dhtmlkitchen@gmail.com>
- CC: Mike Wilson <mikewse@hotmail.com>, Chris Miller <chris@blinkbox.com>, www-style@w3.org
Garrett Smith wrote: >> I am not asking you to use jQuery. >> > > Ah, I see what you're getting at now. > > >> I am asking: do you need a) to change styling [of group] of elements in >> runtime (from script - runtime variability)? >> Or is it about b) redefining some CSS attribute values later in style sheet >> (pure CSS business - load time variability)? >> >> > > CSS Variables [1] RQ3 > > >> What exactly you need CSS Variables for (a or b)? Could you provide real >> case definition where you will benefit >> from them? >> > > (b), for cobranding, as in the CSS Variables[1], RQ1, RQ2, RQ4. (not > that RQ3 is bad or useless in any way). > So you need set of values (parameters) to be defined in one style sheet and be used in other style sheets, correct? That is typical use of constants in programming languages. Why do you need Variables for that? Again: there are two approaches of CSS parametrization: CSS Constants [1] and CSS Variables [2]. Both of the allow to do parametrization of CSS. From implementation point of view CSS Variables are a) significantly more complex, b) "resource greedy" and change current CSS processing principles. That is why I am trying to understand: do CSS Variables bring so much benefits so it is worth implementing them? [1] CSS Constants: http://wiki.csswg.org/ideas/constants [2] CSS Variables: http://disruptive-innovations.com/zoo/cssvariables/ -- Andrew Fedoniouk. http://terrainformatica.com
Received on Monday, 6 October 2008 23:16:42 UTC