- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Mon, 27 Apr 2015 05:49:35 +0200
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: "www-style@w3.org" <www-style@w3.org>, WebApps WG <public-webapps@w3.org>
On Mon, Apr 27, 2015 at 5:37 AM, L. David Baron <dbaron@dbaron.org> wrote: > We haven't really used (in the sense of shipping across browsers) > pseudo-elements before for things that are both tree-like (i.e., not > ::first-letter, ::first-line, or ::selection) and not leaves of the > tree. (Gecko doesn't implement any pseudo-elements that can have > other selectors to their right. I'm not sure if other engines > have.) > > I'd be a little worried about ease of implementation, and doing so > without disabling a bunch of selector-related optimizations that > we'd rather have. > > At some point we probably do want to have this sort of > pseudo-element, but it's certainly adding an additional dependency > on to this spec. Are you saying :host accepts selectors to its right and they would potentially result in a match? Even if that were the case it's still unclear to me how a pseudo-class is justified. Or are you saying the concept of a host element selector is problematic in general? -- https://annevankesteren.nl/
Received on Monday, 27 April 2015 03:49:58 UTC