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

Re: [mediaqueries4][css3-conditional] Whitespace: "and(" vs. "and ("

From: Simon Sapin <simon.sapin@exyr.org>
Date: Sun, 02 Jun 2013 14:43:02 +0900
Message-ID: <51AADB66.5050308@exyr.org>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Simon Sapin <simon.sapin@kozea.fr>, www-style@w3.org
Le 04/10/2012 07:30, Tab Atkins Jr. a écrit :
> On Wed, Oct 3, 2012 at 3:05 PM, Simon Sapin<simon.sapin@kozea.fr>  wrote:
>>> The following is an malformed media query because having no space
>>> between ‘and’ and the expression is not allowed. (That is reserved
>>> for the functional notation syntax.)
>>>
>>> @media all and(color) { … }
>>
>>
>> but the relevant grammar is "AND S* expression". Should the grammar be
>> changed to "AND S+ expression" to capture in normative spec that some
>> whitespace is required there?
>>
>> Whatever we decide here should also apply to css3-conditional’s 'and', 'or',
>> and 'not' operators. (ie: can they be functions?)
> Whitespace is not actually required there.  The following is valid:
>
> @media all and/*wooo!*/(color) { ... }

We changed @supports to require whitespace, so that the spec is less 
misleading. (Since the tokenizer is not in the same spec, a reader might 
not know about function tokens and expect "and(" to be valid.)

http://lists.w3.org/Archives/Public/www-style/2012Dec/0330.html

But this issue still exists in Media Queries. Should we make the same 
change in MQ4?

-- 
Simon Sapin
Received on Sunday, 2 June 2013 05:43:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:12 UTC