W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [css3-conditional] value of CSSSupportsRule.conditionText

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 6 Aug 2012 17:19:07 -0700
Message-ID: <CAAWBYDA34AV2RFMY_Hn5xTSUr1aiRq+hJNciBQLDzRdweA2Qgg@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: "L. David Baron" <dbaron@dbaron.org>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, www-style@w3.org
On Mon, Aug 6, 2012 at 5:05 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> Tab Atkins Jr.:
>> Actually, it'll still work even if we do make it apply to selectors in
>> the future.  The only problem is reserializing, which is easy to
>> detect and insert an empty comment for, as I proposed.
>
> But it doesn't work if you want to allow selectors (or other syntax
> sensitive to a lack of white space between tokens) inside the supports
> condition.  For example with a hypothetical:
>
>   @supports (foopy: select(#a/**/.b/**/)) { ... }
>
> There's no way to know that the comment before the "." needs to be preserved
> while the one after the "b" can be dropped, if your UA doesn't implement
> foopy.  So we would need to preserve all comments within the property value
> parts of the supports condition, at least.

Ah, yes, I see.  You can only trigger the special "insert a comment"
rule if you know that you're in a selector context, and we'd like to
avoid requiring that knowledge.

Okay, then yeah, comments will need to be preserved (at least the
presence of them, though not their contents), unless we change the
rule that allows comments there in the first place. ^_^

~TJ
Received on Tuesday, 7 August 2012 00:19:54 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:58 GMT