W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: Custom pseudo-elements collisions, was: Need a better way to reach into the shadow DOM subtree

From: Dimitri Glazkov <dglazkov@google.com>
Date: Wed, 24 Oct 2012 10:26:24 -0700
Message-ID: <CADh5Ky3NF7vL8RHOhckBXi8uDXr4N=zdkQTtjKnj9icmfEQUaw@mail.gmail.com>
To: François REMY <fremycompany_pub@yahoo.fr>
Cc: Brian Kardell <bkardell@gmail.com>, David Hyatt <hyatt@apple.com>, "www-style@w3.org" <www-style@w3.org>, Tab Atkins <tabatkins@google.com>
On Wed, Oct 24, 2012 at 10:21 AM, François REMY
<fremycompany_pub@yahoo.fr> wrote:
> |  I am re-visiting this -- time to add custom pseudo-elements to Shadow
> |  DOM spec! -- and would like to solicit ideas/opinions on the topic of
> |  collisions.
> I'm in favor of a user prefix. Since 'x-' happens to be the preferred one,
> why not 'x-'.
> However, I'm unsure about your goal here. Do you intend [[ #id::x-element ]]
> to match more than one element? Because if you want this, custom
> pseudo-elements aren't the right tool for you. In that case, you need a
> custom pseudo-class and a "shadow-walking" operator. Something like:
>    #id .. div:x-selected { ... }
> Custom pseudo-classes were already proposed in the past (but died because of
> weak traction) so this isn't a non-sense to reintroduce them now we have
> good use cases for them.

No, custom pseudo-elements match just one element. I think there is a
good use case for custom pseudo-classes, too, but ... one step at a
time :)

Received on Wednesday, 24 October 2012 17:26:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:05 UTC