- From: François REMY <francois.remy.dev@outlook.com>
- Date: Sun, 16 Mar 2014 15:00:30 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>, "Zack Weinberg" <zackw@panix.com>, "Bjoern Hoehrmann" <derhoermi@gmx.net>, "www-style list" <www-style@w3.org>
I'm fine with "--" too. I thought "_" was okay ("FC_BG_COLOR" looks good to
me and is easy enough to type once you remeber there's a CAPSLOCK key on
your keyboard) but "--" (as in "fc--bg-color") is fine too and, you're
right, closer to the usual CSS syntax.
That being said,
> I also think it should
> be required as a prefix, not just a substring anywhere. That has the
> advantage of being easier to check in the parser, as well as enforcing
> some uniformity.
Please no :-(
It's a 95 seconds win for the person authoring the parser, but it's a loss
for the others. Would you mind giving us the possibility to put "--"
anywhere? This encourages custom-namespace-prefixing & looks better to my
eyes (I would even say: why not keep the syntax spec intact and only allow
"--" inside the token, but that's maybe asking too much). By the way, Alan
Stearns mentioned on Twitter using "--" to comment out declarations, and I
think I may have been doing the same in the past; no big deal but worth
mentioning.
PS: Not wanting to open the pandora box again (yet I know I do, sorry) but
there's also the option of keeping everything the same and just renaming
"var" to something generic ("x", "my", "custom", "ud" (for user-defined),
...) that doesn't scream "variables" and could be reused as a prefix
everywhere. If people are afraid of making big changes, this is a easy thing
to do which requires exactly about no change anywhere (and this is a change
more than one person had been requesting in the past, for the exact same
reason Tab mentioned in his opening mail). Just saying.
Received on Sunday, 16 March 2014 14:00:53 UTC