- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Sat, 09 May 2020 00:40:53 +0000
- To: public-css-archive@w3.org
> Given your calendar widget example, imagine week parts as well as day parts. Again, nesting parts isn't possible right now and we probably don't want to make it possible. It exposes internal structure that we probably want to hide. > You're already invented a third thing with the existing part name proposal, ::part(weekend):--selected already uses three concepts, pseudo-element name, part name, and pseudo-class. ::part() isn't a third thing *for the authors of the component to decide on* (or for the users of the component to have to remember which values correspond to it). It's a syntax hack over the pseudo-element name. > And as I mentioned above, it also potentially gives them a way to create native pseudo-elements as well. Something that the existing shadow part proposal can't do. Wouldn't it be useful to allow custom elements to define their own ::marker for example? As far as I can tell, my proposal is perfectly compatible with this idea? What makes you think it isn't? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4900#issuecomment-626076638 using your GitHub account
Received on Saturday, 9 May 2020 00:40:55 UTC