Really appreciate your honest feedback Jordan. Vue has the plus to be more similar to HTML and you can use it just in a static file using CDN. In React you can't bypass a build tool.

To this day it is not fully compatible with Web Components and fails, and has failed many times, to handle certain HTML attributes correctly.

I'm curious, which problem did you encounter with React and WebComponents, and React and HTML attributes?

React currently does not support the inert attribute or fully support hidden. React has a long history of unreliably working with HTML because of its flawed design. React maintainers have forced themselves into a corner where they have to manually update React alongside HTML so if HTML gets something new, like inert, developers can’t use it until React is updated, which is often AFTER the browsers support it. React is effectively the new IE.

It also doesn’t understand Web Components without configuration and some extra coding and even then it’s still not perfect. custom-elements-everywhere.com shows a failing score compared to virtually every other framework, which all score 100%.

Jordan Brennan Never heard of inert attr. It seems that you can use it like this:

<div inert={isInertOn ? "": undefined}/>

github.com/WICG/inert/issues/58

But yes, React compiles to html so dev must rely on the compiler support.

---

I don't often use Web Components but I agree that is a shame that an industry leader library lacks in fundamentals.

It seems that something is moving here github.com/facebook/react/issues/11347

---

Is a shame that an industry leader library lacks in fundamentals.

This is a weird thing, hard to accept honestly, even if 95% of apps never encounter these problems it doesn't mean that these should be ignored.

Great points here Jordan.