W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2020

Re: [csswg-drafts] [css-shadow-parts] Unifying ::part() and ::--foo (#4900)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 May 2020 15:35:42 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-625874327-1588952142-sysbot+gh@w3.org>
> I strongly feel that shadow parts should really just be custom pseudo-elements and have a single tag-like name, just like built-in pseudo elements do. I want to expose built-in behavior not create something special and different.

Note that that's the motivation behind my proposal in the OP; preserve the more useful behavior of class-like names, but also preserve the looks-like-builtin nature of pseudo-element names.

>  If the <custom-day> itself exposes custom state or additional parts, those would simply be exposed and could be selected like:

Recall that we (intentionally) don't allow ::part() nesting - if you want to expose a part of your part, you "forward" their part into your part-map.  This hides details of the internal structure of the element.

(It also avoids the oddity of a sub-component exposing nested parts, but `<parent part=foo><child part=bar></child></parent>` exposing "foo" and "bar" as siblings, not nested. And we don't want to get into the hornet's nest of distinguishing "real" children from sub-components part "children"...)

GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4900#issuecomment-625874327 using your GitHub account
Received on Friday, 8 May 2020 15:35:45 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:06 UTC