Re: [w3c/webcomponents] Theming options for shadow roots (#864)

@justinfagnani : that's an interesting insight. The two broad category roughly matches what I pointed out somewhere in the past (I can't find it right now):
 - Reusable component that needs to have strict control over the stability of each element in its implementation
 - Structural application specific component that needs a lot of flexibility in its styling

The issue of mapping a specific range of values  / subset of values to a *native* property is also pretty much a superset of issues I pointed out about [filtering the set of properties](https://github.com/w3c/webcomponents/issues/864#issuecomment-579566210).

So we're in a board agreement in terms of the set of problems at hands.

It would be really good if you can somehow compile a set of requirements for these two board categories of components styling use cases (with a concrete use case like a calendar widget with stylable current day indicator).

I'd also say that the issue of having to restrict a specific set of allowed values is very akin to the one [registered CSS property](https://drafts.css-houdini.org/css-properties-values-api-1/#the-registerproperty-function) is trying to solve in Houdini. I'm not necessarily suggesting or endorsing registered property as an API we should have, but we should definitely pay attention to how they tackled this problem on their side.

-- 
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/864#issuecomment-601967826