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

Just some quick input as a user - another case where I've found `@apply` currently falls apart is with composition. Eg: I have an element that exposes a mixin, I apply a 'base theme' to that element in my app, I want to add extra styles on top of that base theme in a specific instance of the element. Right now if  I `@apply` another mixin on the element it clobbers the base theme.

A workaround for explicit inheritance for `@apply` was discussed at https://github.com/tabatkins/specs/issues/49, though the proposed syntax is perhaps a little unintuitive for users, whereas composition with parts (should?) 'just work'.

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