Re: [csswg-drafts] [css-nesting] add note explaining that `&__element` isn't valid and why (#3748) from jonjohnjohnson via GitHub on 2019-03-20 (public-css-archive@w3.org from March 2019)

From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Mar 2019 00:22:18 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-474635062-1553041337-sysbot+gh@w3.org>

I think your example selector might actually be valid, but attempting to match an invalid element with type `__element`. Equivalent to `__element.block`. 😆 

> The nesting selector is allowed anywhere in a compound selector, even before a type selector, violating the normal restrictions on ordering within a compound selector. [...] An ampersand is unambiguously separable from an ident, tho, so there is no problem with it preceding a type selector, like &div. - https://drafts.csswg.org/css-nesting-1/#nest-selector

-- 
GitHub Notification of comment by jonjohnjohnson
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3748#issuecomment-474635062 using your GitHub account

Received on Wednesday, 20 March 2019 00:22:20 UTC