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

> @michaelwarren1106 I'm sorry, I don't understand how "theming" is relevant here? It sounds like a totally different problem, and it was only mentioned in [one](https://github.com/WICG/webcomponents/issues/1052#issuecomment-2012430419) of the several use-cases above.

@mayank99 this is what I've been trying to get across in comments like this: https://github.com/WICG/webcomponents/issues/1052#issuecomment-2008393434

> But also... theming is different from open-stylable. Open stylable is a proposal to solve a problem affecting components migrating from light DOM to shadow DOM. There are still lots of other problems around theming that are better solved, IMO, with specific theming APIs that don't require completely opening up a shadow root to styles, and work with ::part().

The reason why theming has come up in relation to Open Styleable recently is in part to _try_ to separate the two because there were so many theming use cases brought into #909 and meetings around Open Styleable. IMO, people want better theming solutions so badly that they're hoping that anything, including Open Styleable, can help them, even though I think theming is quite a different problem.

> In my mind, "theming" is already solved by CSS features like `color-scheme` and style queries.

Many people need to be able to arbitrarily style allowed elements deep down the shadow tree. That isn't solved by anything today. Custom CSS properties have to be mapped by the component author, and `::part()` doesn't work deeply. `::theme()` was proposal long ago to solve this, but we haven't worked out the exact requirements for being able to filter on specific hosts, parts, etc.

There's also a lot of potential in CSS mixins and functions to help with theming use cases (ie, translate a design token CSS variable in multiple concrete native properties, or a high-level token into several low-level tokens, or apply a user-defined mixin to a selector in a component) - but we'll need mixins and functions to work across shadow DOM boundaries.

> Does anybody have a link to a recent comment/discussion somewhere that further explains how the two topics are related?

In https://github.com/WICG/webcomponents/issues/1065#issuecomment-2284597499 I was trying to suggest discussing theming _separate_ from open styleable, which is part of how we got here. https://github.com/w3c/tpac2024-breakouts/issues/27 has both though. I'm happy to alternatively discuss _just_ Open Styleable if people think we can get closer to a concrete proposal in that time.

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

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