1
point
jetin
Joined 5 karma
Front-end developer. Working with CSS, vanilla JS, React, Next.js. I implement responsive, accessible, backward-compatible interfaces.
https://www.jeantinland.com/
- jetinI also agree with you, I simply think the need for shadow root depends on the level of encapsulation you need.
- Interesting article, I think some points are covered by this ESlint plugin [0] specifically created for web components.
- Yeah, I also used the Shadow DOM a lot working on a CMS that edit the website content “in place”: CMS UI was safely scoped inside my web components thanks to their Shadow roots, I never had to worry about arbitrary styles from the websites the CMS was loaded in colliding with internal CSS.
Shadow DOM exists for some specific use cases but it shouldn’t systematically used when creating web components.