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

> Sure we can.  And when you do want to block, that's what `all: initial` is for.  (Alternately, an equivalent of `all` for just custom properties has been proposed; it would be called `--`, as in `--: initial`.) You can then let particular custom properties thru with `--foo: inherit`.

That's such a cumbersome API.  So if an author wanted to use a component and didn't want to expose any custom properties to it, then he/she has to do `--: initial` and selectively expose custom property.  That's too much complexity just to style a part of component.

> Nesting is familiar to users of every single CSS preprocessor in existence, and is consistently one of the most popular and highly used features. The learning curve here is miniscule based on practical evidence.

I disagree.  Nesting declarations of pseudo-class selectors inside custom mixins  is extremely confusing.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/300#issuecomment-144570887