- From: Matthew Phillips <notifications@github.com>
- Date: Sat, 16 Mar 2024 08:08:52 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 16 March 2024 15:08:56 UTC
_Note that GitHub's quoting mechanism seems to be broken at the moment so I'm omitting some quotes here unfortunately_ @DarkWiiPlayer I'm fine with this the definition of "opt-in", 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-2002014557 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/2002014557@github.com>
Received on Saturday, 16 March 2024 15:08:56 UTC