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

Ah, yes, custom properties cascade like every other property does, with one value winning per element; the fact that one of them might contain a declaration block intended to be sent to an `@apply` doesn't change things.

I have a proposal for some [cascade controls](https://tabatkins.github.io/specs/css-cascade-control/) that would let a property "merge" with its earlier-in-the-cascade variants; if the custom property was appropriately typed as carrying a declaration list (we don't have a type for that in [Custom Properties & Values](https://drafts.css-houdini.org/css-properties-values-api/) yet, but we'll add it when `@apply` is officially accepted), then `--my-mixin+: {...};` would work. (It would be considered a list-valued property, I guess, just with a different delimiter than normal.)

-- 
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-262107156