- From: James Hopkins <james@idreamincode.co.uk>
- Date: Fri, 13 Feb 2009 19:40:55 +0000
- To: Biju Gm@il <bijumaillist@gmail.com>
- Cc: SimDigital - Gustavo Villa <gustavo@simdigital.com.br>, www-style@w3.org
On 13 Feb 2009, at 04:42, Biju Gm@il wrote:
>
> On Thu, Feb 12, 2009 at 6:57 PM, James Hopkins <james@idreamincode.co.uk
> > wrote:
>>
>> This is covered by both Dave Hyatts & Daniel Glazmans proposal for
>> Variables
>> (http://disruptive-innovations.com/zoo/cssvariables/) and subsequent
>> counter-proposal by fantasai
>> (http://fantasai.inkedblade.net/style/specs/constants/). I recently
>> wrote a
>> comparison of both proposals which can be found at CSS3.Info
>> (http://www.css3.info/summary-of-the-two-current-css-constants-proposals/
>> ).
>>
>> Hope this helps, and welcome to the mailing list :)
>>
>> James
>
> can I assume on fantasai's proposal
>
> ..notebox {
> `box;
> }
> @define values {
> accentColor: orange;
> altBG: yellow;
> }
> ..warningbox {
> `box;
> }
>
> "box" should be corrected as "notebox", ie
>
> ..notebox {
> `notebox;
> }
> @define values {
> accentColor: orange;
> altBG: yellow;
> }
> ..warningbox {
> `notebox;
> }
>
No - the (complete) example demonstrates primarily how, in this case,
subsequent 'value' @define rules further down the snippet (from the
initial 'value' @define declaration), have a stronger influence in the
cascade for the constant values that those rules define. Note how for
the '.notebox' block, the `accentColor value will be 'blue' (defined
in the initial Value constant declaration) and the background color
will be 'white' (defined in the P element block) - whereas for the
'.warningbox' block, the `accentColor value will be
'orange' (redefined in the second Value constant declaration), and the
background color will be 'yellow' (as this value for altBG is defined
in this second declaration also).
>
Received on Friday, 13 February 2009 19:41:37 UTC