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

Yeah, I think the TLDR (please correct me if I'm wrong or expand as necessary) is that we ended up deciding to focus on an initial version of an API which allows the page's author to mark a subset of the document-level stylesheets to be included inside shadow trees.

The shadow root need to opt into this as well (probably via a new `ShadowRootInit` attribute or a different `ShadowRootMode`).

Things that got discussed and need details / design:

 * API shape (I think a new `<link>` / `<style>` attribute is the most obvious option but...).
 * Letting the page author set where in the cascade would these go. Seems there are valid use cases to import at a low priority ("base" styles) and at a high priority ("theming" styles).

Things that would be nice to have:

 * Letting the component author somehow override how they are layered.
 * (probably a bunch of others I can't remember off the top of my head)

Importantly, that doesn't mean that this problem is dealt with completely once we provide such API, but seems it cover the biggest / most common use cases, and we can work on solving more complex use cases incrementally after this.

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

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