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

Yes, I understand that we need to expose particular parts for styling; that's addressed equally well with v/a/n or ::part.  (With v/a/n, you document several variables, and use each within an appropriate selector, like `h1 { @apply --heading; }`.  With ::part(), you expose the relevant element as a visible part, I presume with something like `<h1 part=heading>`.)

What, specifically, do you think is hard with one or the other solution?

> I don't see why we need to re-invent the wheel to replace that solution.

No matter what we do, we're going to be reinventing things.  We will **not** produce a solution that allows for a 100% fidelity recreation of the current form pseudo-element stuff, because that immediately runs into namespace issues. Current form controls also only touch on a small subset of the possibility space, while ::part() needs to address a bunch more cases (I outlined some in a previous comment).

So lots of invention have to happen no matter what.

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