- From: Jared White <notifications@github.com>
- Date: Wed, 08 Nov 2023 09:40:30 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 8 November 2023 17:40:36 UTC
Clearly there's enough demand for this feature that it should be considered seriously. But I am personally unhappy with the unwillingness to embrace new platform paradigms offering truly useful and valid features because…Tailwind? Bootstrap. Yikes. I wish we could jettison legacy ideas of "all my CSS is always global" just as emphatically as we jettisoned float-based layouts or fixed-width templates or pixel sizing. As we've seen, it actually *is* possible to bring shared styles into shadow DOMs. The fact you can't do it "by default" is a feature, not a bug. I already know mine won't be a popular opinion, but I'm sharing this because some people will wander into discussions like this and get the impression that "shadow DOM will break my website templates, yuck" and that's _just not true_. It merely takes some new up-front architectural work, work that people *should* learn how to do as a vital 2023+ CSS skill. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-1802359529 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/1802359529@github.com>
Received on Wednesday, 8 November 2023 17:40:36 UTC