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

@DarkWiiPlayer 

> I think it's important to consider where the attribute is and who is in charge of setting it. The <template> element would normally be rendered by the component itself, via some sort of server-side rendering mechanism. This is different than the global CSS having to consider the component.

> The point here is for a component author to provide a component that, without any further changes from the user, can be dropped into a website and adopt the website's styling. So an opt-in from within the component is perfectly in line with the goals of this proposal, while an opt-in by the website author is not.

> The <template> is really just a special case of attachShadow, where the component provides some server-side code to pre-render the contents of its shadow-DOM, but in these cases the attribute on the <template> is still under the control of the component author.

I'm fine with this the definition, so going back to @justinfagnani's comment:

> I thought an attribute might be tenable here for the layer approach, but the original idea is to not require any opt-in from the page.

What proposals in this thread require an opt-in from the page, if we agree to @DarkWiiPlayer's definition of opt-in? A server-side component framework can add CSS to a page just as easily as it can add an attribute to an element. Am I missing something? All of these proposals seem equally viable as far as this requirement is concerned, to me.

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

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