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

Re: CSS Hierarchies / Selector Nesting Proposal

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 2 Jun 2011 21:38:54 -0700
Message-ID: <BANLkTikRXfc0YZKXr-YuHO9VwOezyXFsHQ@mail.gmail.com>
To: Eli Morris-Heft <eli.morris.heft@gmail.com>
Cc: "www-style@w3.org" <www-style@w3.org>
On Thu, Jun 2, 2011 at 12:40 PM, Eli Morris-Heft
<eli.morris.heft@gmail.com> wrote:
> On a totally different note, in this plan, what happens if there is an
> ampersand in an unnested selector:
> &.bar { /* ... */ }
> My guess is that is just acts as if the ampersand is not there. I suppose
> it's fairly easy to build the parser so that it handles these correctly
> (correctly being that each of these selectors matches every .bar, assuming
> people agree with my suggestion of how to handle the case of "&.bar"):
> &.bar { /* ... */ }
> & .bar { /*...*/)

Nah, it's just a syntax error (that is, an invalid selector, with the
error-correction behavior that implies).  It makes no sense to use
nesting syntax when you're not nesting.

~TJ
Received on Friday, 3 June 2011 04:39:41 GMT

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