Re: [css-variables] Custom properties using the 'var' prefix? (Issue 1, !important)

Sorry Sylvain if the wording sound wrong to you. What I wanted to say is that I originally promoted the 'x' prefix but that, when it has been objected, I started looking at alternatives by looking on the web at previous attempts to use or define custom properties in CSS, and found the 'my' prefix to be the most frequently used by far. So, I decided to go with it and Brian didn't object.
 However, I'm still fine with the 'x' prefix. As Brian noted, the 'x' prefix is currently in use in the Web Components working draft (https://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html). The 'c' prefix (short from of 'custom') or any other one-letter prefix would also be an option, but it would maybe sound less natural to most developers. The 'user' prefix once was considered but it's poisoned by 'user-select'.
 
However, those naming issues are bringing us further and further from the core issue that seems to be the definition itself of the [css-variables] concept... 
 
 

 
----- Mail original -----
De : Sylvain Galineau <sylvaing@microsoft.com>
À : François REMY <fremycompany_pub@yahoo.fr>
Cc : "www-style@w3.org" <www-style@w3.org>
Envoyé le : Vendredi 7 septembre 2012 17h20
Objet : RE: [css-variables] Custom properties using the 'var' prefix? (Issue 1, !important)


[François REMY:]
> If you correctly remember, I was proposing the 'x' prefix beforehand but 
>Sylvain said he didn't like it, which is why I did all this research in 
>first place. If we can agree on the 'x' prefix, I would not mind at all.
> 
That someone does not like something is irrelevant; why they don't is all 
that matters. In this case, the x- prefixed was modeled after the IETF's 
X- prefix which the IETF is phasing out. I don't think we should use 
patterns others are getting rid of for good reasons, so I objected.

Received on Friday, 7 September 2012 16:14:19 UTC