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

Re: [css-variables] Slight tweak to value space of CSS variables

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 28 May 2013 08:43:50 -0700
Message-ID: <CAAWBYDA724zuSN0+ZaxY_wHc0+eX61WB=3tMCQG2Y9_99zsCOQ@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: Simon Sapin <simon.sapin@exyr.org>, www-style list <www-style@w3.org>
On Sun, May 26, 2013 at 10:51 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Wednesday 2013-05-22 13:38 +0800, Simon Sapin wrote:
>> I’d be fine with a note that says exactly what is *not* allowed.
>> Something like this, although of course the list could be tweaked:
>>
>>     A custom property declaration is ignored if it contains a <i>bad
>> token</i>. A <dfn>bad token</dfn> is a BAD_STRING token, BAD_URL
>> token, BAD_COMMENT token[1], unmatched '}' token, unmatched ']'
>> token, unmatched ')' token, or a block or function that contains a
>> <i>bad token</i>.
>
> One problem here is that CSS 2.1 produces BAD_STRING and BAD_URL at
> end-of-file, when our current end-of-file handling rules say that
> strings and URLs should in fact be valid.  (Though I'm tending
> towards thinking that change may have been a mistake.)
>
> It might actually make more sense to fix that in 2.1 than trying to
> work around it in variables.
>
> Otherwise this seems reasonable to me.

Note that Syntax produces valid strings and url tokens at EOF.

~TJ
Received on Tuesday, 28 May 2013 15:44:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 28 May 2013 15:44:44 UTC