- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 5 Feb 2013 13:05:47 -0800
- To: François REMY <francois.remy.dev@outlook.com>
- Cc: Simon Sapin <simon.sapin@kozea.fr>, www-style list <www-style@w3.org>
On Tue, Feb 5, 2013 at 12:55 PM, François REMY <francois.remy.dev@outlook.com> wrote: >> css3-syntax now has a more precise definition of how to turn text into >> tokens, and tokens into "component values" (which were known as >> "primitives" in the draft until recently.) > > Nice! However, I still have one use case in mind the new syntax doesn't solve (in an elegant way): the operator symbols. > > selector { > a: if(get(b)==none && get(c)<=2) { 0% } else { 100% }; > b: some; > c: 3; > } > > sub-selector { > b: none; > c: 1; > } > > I would prefer the grammar of a property value to accept any token inside a block except block terminators <},],)> and not just a limited subset of tokens. But if there's a good reason to limit the subset, that's fine. Again, with what I said in my original reply, that's exactly what will happen. ~TJ
Received on Tuesday, 5 February 2013 21:06:35 UTC