- From: Wii <notifications@github.com>
- Date: Sat, 16 Mar 2024 10:40:01 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/909/2002058862@github.com>
> A server-side component framework can add CSS to a page just as easily as it can add an attribute to an element. I think you're conflating two ideas here: In cases where the entire content generation of a site is handled by a single framework, then that framework could easily insert code at several points, meaning it could create a custom element *and* add corresponding CSS elsewhere to push styles into it. This much is correct. However, you're reducing the entire feature to this specific case. The point of web component is precisely to *not* depend on this type of architecture where a single framework controls the entire stack, but where component authors can independently write framework-agnostic components that any website can just use. In the most basic case, a website is written in plain HTML and CSS, and the author simply loads a JS module from jsdelivr and starts adding `<custom-element>`s to their document, and expect the `<button>`s inside the shadow-dom to look the way they do in the rest of the site. Please keep in mind that the web spans a massive range of scales and architectures, from massive companies like google who have the resources to just built their own entire framework to handle things coherently, to the gym around the corner giving 50€ to the owner's 16yo nephew to build them *a* website. Web components should aim to work for *all* of them :) -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-2002058862 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/2002058862@github.com>
Received on Saturday, 16 March 2024 17:40:05 UTC