W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: [css-syntax] value grammar, <value> type and browser implementations

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 5 Feb 2013 13:05:47 -0800
Message-ID: <CAAWBYDAgtmLBv5yGPbZ1_LbnUe3ea7iuWNbFLuqfO9C6pAL74w@mail.gmail.com>
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 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:05 GMT