Re: CSS Hierarchies / Selector Nesting Proposal

On Thu, Jun 2, 2011 at 12:40 PM, Eli Morris-Heft
<> 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.


Received on Friday, 3 June 2011 04:39:41 UTC