Glad to hear I am not the only one. My goal (too) is for it to on defined (or imported) once and used in each element that needs it. Let's push things in that direction in the spec'ing process!! 💪
My understanding is that the team working on this things at Edge are looking to pivot to HTML Module Scripts as soon as they can get the Declarative CSS Module Scripts work on the path to shipping. 🤞
I love it when a plan comes together!!
`:host:has(...) {}` is now shipping in Chromium! 🪄 💫 ✨
@TheIdOfAlan As with all things, trade-offs, but it's cool to see all the different parts of the web stack wherein people are experimenting with #webComponents. If you're ever interested, the #webComponentCG gathers in https://discord.gg/xYXS6RZ7 to chat leveraging current APIs, shaping future APIs, and supporting each other in making awesome things...
Thanks for sharing!! 🪄 💫 ✨
Let's use case the web forward! Who's with me?
#webComponentCG #webComponents #shadowDOM #customElements #communityProtocols #w3c #wicg #html #css #js #andMore
@jamienk I think you're hitting on various important points here:
> why can't I find them?
The #webComponentCG has attempted to relaunch webcomponents.org, be the volunteers were all quite busy...building #webComponents instead 🙈
> various frameworks
I'm not sure I'd call #shoelace tied to a framework, but it is a family of components. Often building a family offsets the cost of building one component in a web ecosystem that's been prioritizing CSS improvements over DOM primitives, lately
1/x
westbrook