W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

[csswg-drafts] [css-shadow-parts] ::part(foo)::part(bar) instead of forwarding? (#3841)

From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
Date: Thu, 18 Apr 2019 12:17:13 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-434740392-1555589831-sysbot+gh@w3.org>
emilio has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-shadow-parts] ::part(foo)::part(bar) instead of forwarding? ==
I was going through the shadow parts spec, and it seems to me like a better alternative to complex part-forwarding micro-syntaxes (albeit maybe a bit more simplistic?) could be just to allow multiple `::part()` selectors.

So you would do `::part(filepicker)::part(button)` rather than `::part(filepicker-button)` or what not. Whether (or which) parts or a sub-component are exposed could still be controlled the same way `exportparts` works.

Seems to me the model would be much more consistent. Also, this is much easier (seems to me, at least, while I've been poking at this) implementation-wise, since you don't need to concatenate part names around to figure out if a part matches from a given tree. Stuff would just work.

Has this approach been considered?

// cc @fergald @rniwa @tabatkins 

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3841 using your GitHub account
Received on Thursday, 18 April 2019 12:17:14 UTC

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