W3C home > Mailing lists > Public > www-style@w3.org > March 2008

Re: [css3-mediaqueries] media queries grammar

From: Andrei Polushin <polushin@gmail.com>
Date: Tue, 11 Mar 2008 18:46:05 +0600
Message-ID: <6b7fe1730803110546q4964cb08ne35edcc05fa67abb@mail.gmail.com>
To: www-style@w3.org

2008/2/5, Bert Bos wrote:
>  I had an action in the CSs WG to look at the syntax of media queries
>  [...]
>  I replaced the S+ by S*. The difference is that the latter allows
>
>     not/* and I mean not! */print
>  and
>     ... (color)and
>
>  while the former requires at least one space. (I'm not saying users
>  *should* write queries like that. I just don't see a reason to disallow
>  it. But note that "... and(color)" is not correct, because it is a
>  functional notation.)

There was a request for discussion on this, by Anne van Kesteren, at
<http://lists.w3.org/Archives/Public/www-style/2007Dec/0038.html>:

> * It needs to be clear where whitespace is required. I made it required
> between "and" and "(width)" for instance in the tests so they can not be
> confused with CSS function definitions, but maybe this is worth some
> discussion given that implementations disagree.

Was there such a discussion, or a formal decision on this, or not yet?

I would prefer to re-allow whitespace between the CSS function name
and the opening '(', i.e. to split the FUNCTION token. It might sound
too radical, but what was the reason to disallow it in past?
Otherwise, and as a consequence, now it's hard to allow an optional
whitespace in such a non-functional context.

--
Andrei Polushin
Received on Tuesday, 11 March 2008 12:53:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:02 GMT