Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)

@jaredcwhite I appreciate the sentiment and basically agree for greenfield projects, but I think we _must_ consider how real projects can get to a place where they can use modern features.

> unwillingness

I wouldn't mark this down to "unwillingness". We must recognize that real-world developers have real-world constraints, and often their own customers with their own constraints. The component authors who need this feature might very well _want_ to use shadow DOM, but _can't_. In particular, their customers might have existing stylesheets that need to work.

We also need to recognize that the current state of styling with shadow DOM does not match the abilities of non-shadow DOM styling. There's no deep theme support still, and components can't style their own light DOM grand children. Until those things are addressed, shadow DOM might not be suitable for everyone. _Yet_ shadow DOM is the only way we have to do interoperable composition. So some developers are currently left with a choice between composition and style encapsulation, and unfortunately given that choice many of them just choose not to use web components at all: they can't use style encapsulation, so they get composition by requiring a specific framework.

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

Message ID: <WICG/webcomponents/issues/909/1802514117@github.com>