Is it worth creating web components that work on IE 11? Or Edge?
I spent the last week on my least favorite engineering task: trying to get a body of code that works on Chrome/Safari/Firefox to work on Microsoft Edge and Microsoft Internet Explorer. In this case, I've been trying to get the Elix project's unit tests and basic component set working as expected in Edge and IE 11. Such work is never fun. Lately I've been wondering whether it's worth the Elix project's time to support Microsoft's browsers.
Your web components with Shadow DOM may need to update light DOM too
Web components and Shadow DOM are practically synonymous, but even web components with a shadow subtree often need to render information into the light DOM. A component might need to:
Perhaps you like the benefits of functional reactive programming, but would
like to create native web components with minimal overhead. This post explores
functional reactive programming (FRP) style modeled after React. This mixin
focuses exclusively on managing state and determining when the state should be
rendered. You can use this mixin with whatever DOM rendering technology you
like: virtual-dom, hyperHTML, lit-html, plain old DOM API calls, etc.