- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 28 Aug 2012 13:38:41 -0700
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: Brian Kardell <bkardell@gmail.com>, fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On Tue, Aug 28, 2012 at 1:21 PM, L. David Baron <dbaron@dbaron.org> wrote: > On Tuesday 2012-08-28 12:37 -0700, Tab Atkins Jr. wrote: >> The point is that, as currently implemented, whenever I see a ! in a >> rule, I need to push it into a substack, along with all subsequent >> whitespace and comment tokens, until I see a token that's neither >> whitespace nor a comment. If it's an IDENT(important), I throw away >> the stack and make the declaration important. If it's anything else, >> I insert the entire stack into the declaration's value. >> >> This isn't hard. It is, however, inelegant and *useless*. There is >> absolutely no reason to allow this, and it would simplify parsers the >> spec and parsers to disallow it. There shouldn't be any compat impact >> to the change. > > Why should we allow ! within values? It seems already somewhat > established as a delimiter. Can't it just always end the value at > the !, and then make the thing after it make the declaration invalid > if it's something other than IDENT(important)? I'm amused that your alternative to my syntax change is a larger syntax change. ^_^ This is slightly less good for variables, which might want to include ! characters for some reason (when passing values around for JS, say). ~TJ
Received on Tuesday, 28 August 2012 20:39:28 UTC