- From: Wii <notifications@github.com>
- Date: Mon, 18 Mar 2024 14:44:06 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 18 March 2024 21:44:10 UTC
This is close to just being a variation of the second user story from that comment, but applied to my everyday work experience: > When developing web applications for internal use, I want to re-use web components that represent common logic across various projects regardless of what tech stack they individually use. When frameworks are used that require extra classes, I want to extend the components to use templates and have the framework classes available automatically inside the component. It *might* be worth pointing out that mixins will eventually make their way into CSS, so depending on what the specifics end up being, the case where a framework needs classes might be alleviated by the ability to apply these classes to plain elements as mixins. Although I didn't see too much enthusiasm for the idea of allowing classes as mixins directly. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-2005088249 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/2005088249@github.com>
Received on Monday, 18 March 2024 21:44:10 UTC