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

Re: [css-variables] status ?

From: François REMY <fremycompany_pub@yahoo.fr>
Date: Fri, 25 May 2012 20:35:23 +0200
Message-ID: <E475D190F24C46D0A98CC407951D9F2E@FREMYD2>
To: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>, "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "Daniel Glazman" <daniel.glazman@disruptive-innovations.com>, <www-style@w3.org>
Because we want our code to be understandable. You know that 'bp' means 
background-position in your code, but I don't. And I (or anybody else) will 
have to work with your CSS files after you.

Also, you may have set 'bp' to be background position, but I may have 
another file where 'bp' is set to border-padding. How do we fix that mess?

-----Message d'origine----- 
From: Marat Tanalin | tanalin.com
Sent: Friday, May 25, 2012 8:16 PM
To: Tab Atkins Jr.
Cc: Daniel Glazman ; www-style@w3.org
Subject: Re: [css-variables] status ?

It's a shame. Actually _each_ property could be shortened, especially 
non-shorthand ones, e.g.:

    background-position => $bp
    font-family => $ff
    line-height => $lh
    word-wrap   => $wr

Why not just expand CSS variables to use them anywhere?
Or at least not just in property values, but in property names too?

What are exact issues with it (if any)?
Why hardly limit the feature (variables in this case) immediately as fast as 
it's invented?

Received on Friday, 25 May 2012 18:35:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:16 UTC