Re: [WICG/webcomponents] [open-stylable] Collection of user stories (Issue #1052)

@justinfagnani Thank you for the added context, that is very helpful. It makes sense that theming use-cases should be separate from the other open-styleable use-cases. Still, I think of open-styleable as a general solution that _should_ tackle a broad range of problems. That's why I suggested expanding your initial open-styleable proposal with `@sheet` in https://github.com/WICG/webcomponents/issues/909#issuecomment-2042059261.

It's also worth noting that open-styleable is not the endgame. After introducing open-styleable, we can still have new APIs that are more tailored to specific use-cases.

---

If we're exploring mixins and functions as a way to solve theming, shouldn't we wait before discussing any new shadow-specific theming APIs (`::theme()` or otherwise)?

I'm also glad you said "we'll need mixins and functions to work across shadow DOM boundaries", because that's a great example of a modern feature that would work well with open-styleable. You can imagine shadow-roots opting into a page stylesheet that contains theming-relevant mixins and functions. Mixins and functions don't cascade (unlike custom properties), so this feels like the natural way to include them across shadow boundaries.

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

Message ID: <WICG/webcomponents/issues/1052/2329828399@github.com>