W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: :host pseudo-class

From: Elliott Sprehn <esprehn@chromium.org>
Date: Thu, 30 Apr 2015 22:39:54 -0700
Message-ID: <CAO9Q3iJ7=e5EsZPJXq+71koOTY63vTTHU1NOsPLQaKoEb3DkEA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "www-style@w3.org" <www-style@w3.org>, "L. David Baron" <dbaron@dbaron.org>, WebApps WG <public-webapps@w3.org>
On Thu, Apr 30, 2015 at 10:25 PM, Anne van Kesteren <annevk@annevk.nl>
wrote:

> ...
>
> >> My problem is not with the ability to address the host element, but by
> >> addressing it through a pseudo-class, which has so far only been used
> >> for matching elements in the tree that have a particular internal
> >> slot.
> >
> > I don't understand what distinction you're trying to draw here.  Can
> > you elaborate?
>
> A pseudo-class selector is like a class selector. You match an element
> based on a particular trait it has. Your suggestion for :host()
> however is to make it match an element that cannot otherwise be
> matched. That's vastly different semantics
>

That's still true if you use ::host, what is the thing on the left hand
side the ::host lives on? I'm not aware of any pseudo element that's not
connected to another element such that you couldn't write {thing}::pseudo.

- E
Received on Friday, 1 May 2015 05:41:02 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC