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

Re: CSS Hierarchies / Selector Nesting Proposal

From: Brad Kemper <brad.kemper@gmail.com>
Date: Thu, 2 Jun 2011 08:16:01 -0700
Cc: www-style@w3.org
Message-Id: <293F147C-D34F-4248-A2CC-D9745415E0DE@gmail.com>
To: Boris Zbarsky <bzbarsky@MIT.EDU>

On Jun 2, 2011, at 8:06 AM, Boris Zbarsky wrote:

> On 6/2/11 10:36 AM, Brad Kemper wrote:
>> Why? It looks clear enough (and eminently parse-able) to me to do this:
>> 
>> foo {
>>  &  bar, far, :hover {
>>    prop: val;
>>  }
>> }
> 
> Is it clear and parseable enough to allow:
> 
>  foo {
>    & > bar, > far, ~:hover {
>      prop: val;
>    }
>  }
> 
> ?

I would say so (it seems unambiguous), but I've never written a parser. I am assuming that the purpose of the "&" is so that you don't start trying to read 'bar' as a property and then kick into error handling mode when there is no colon in the right place. But once you have it starting the line, I'd think you'd be into 'inner selector' mode and proceed from there. But if you disagree, then I am interested in hearing why.
Received on Thursday, 2 June 2011 15:16:31 GMT

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