Re: [w3c/webcomponents] Support Custom Pseudo-elements (#300)

> (2) It seems like ::theme() is only useful for open mode shadow DOMs that have not done appropriate forwarding for further shadow DOMs that they contain. Is that really a big enough use case? The forwarding feature seems like a cleaner way to handle this, and one that also works with closed-mode shadow DOMs.

I thought the same thing reading the initial draft.

> One of the objections I heard from Polymer folk about dropping @apply for ::part() was that is made it more difficult to style all the buttons on the page, or similar. This was easy with @apply - just set --button-styles: {...}; and you were good - unless someone in the chain explicitly blocks that property, every button in the subtree will receive the styling.

I wouldn't want the outcome of dropping `@apply` for `::part()`. My understanding is that both are candidates for standardization still and that neither supersedes the other--is that right? I think each style option: custom properties, `@apply` with custom property sets, and named `::part`s are differently useful and each could be individually selected for a component based on what's most appropriate or combined together facilitate different levels of customization.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/300#issuecomment-278742739