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

>  want some kind of composition but they dont want shadow dom

Yeah, I've seen this a lot as well, and unfortunately, I think different needs often get conflated. If we separate the concepts of structural and presentational composition, this becomes clear.

Purely for presentation, one could imagine CSS additions that could probably accomplish this. Think of something like a super-powered version of `order` with a targeting mechanism, e.g. `project: #foo; project-order: 5;`. For presentation alone, you probably wouldn't need the isolated DOM tree that Shadow DOM provides.

However, for structural composition you (almost certainly) need the separate Shadow DOM tree. This allows adding children to a shadow host without having to consider its (private) Shadow DOM tree. This is really the super power that unlocks seamless composition and allows web components to be used without issue in any framework templating engine. 

Unfortunately, it's this separate private DOM tree that introduces something new into the CSS landscape and provokes all the needs noted in this issue.

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

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