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

Re: [css-cascade] Allowing @import to be conditional on @supports queries

From: fantasai <fantasai.lists@inkedblade.net>
Date: Sun, 22 Mar 2015 17:43:09 -0700
Message-ID: <550F619D.5060600@inkedblade.net>
To: Florian Rivoal <florian@rivoal.net>, "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>
On 03/20/2015 01:44 PM, Florian Rivoal wrote:
>
>> On 20 Mar 2015, at 18:52, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>>
>> On Fri, Mar 20, 2015 at 4:34 AM, Florian Rivoal <florian@rivoal.net> wrote:
>>> One of the downside of this is that it requires double parentheses in simple cases:
>>>
>>> @import "http://example.com/foo.css" supports((display:flex));
>>>
>>> It made sense to mandate the parentheses in the @support rule, but they seem overkill here, and is probably surprising for authors. We could do:
>>>
>>> @import <url> [ supports(<supports-condition> | <declaration>) ]? <media-query-list>? ;
>>>
>>> which would let you write:
>>>
>>> @import "http://example.com/foo.css" supports(display:flex);
>>
>> I think fantasai brought this up as well.  I can go either way, though
>> I'll note that we explicitly rejected this for CSS.supports().
>
>
> I forgot about that CSS.supports() is a little bit different though:
>
> CSS.supports("(display: flex)")
>
> The language boundary introduced by the quotes makes it a little bit less silly
> in my mind to have to keep the parens.
>
> But I agree the difference isn't that strong.

I think they're all silly and would prefer that we allowed dropping the
unnecessary parens in all such cases.

~fantasai
Received on Monday, 23 March 2015 00:43:41 UTC

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