everything you've said only advocates for a style scoping, which has many simpler solutions than shadow dom

Yeah that's my point, before you just needed to handle browser idiosyncrasies

Well the point of encapsulation is that it's not your choice. It does feel like a way for companies to DRM their sites more basically

Video controls are super weird it's true.
Why should user land apps auto hide their contents so.

If apps are just `<my-app />`
It feels different no?

That's cute and all, but not a fan of breaking changes. Especially things that affect the accessibility tree.

You can't query selector an input element. But you rendered an input element in the dom. So now you have to write and run extra code to get input elements. i.e. breaking change. There is another thread where someone showcases exactly that.

In your screenshot it didn't pick up the word "minutes"
At least it happens on device without network

This is an indirectly breaking change on the web 😕

imo, should not have shipped in browsers, should have been a JSSugar feature

😢 is that the main reason? We have up so much for so little

Was trying to have an accumulator populated outside of an iterator function

If that’s web, curious how much is dom update time and React overhead vs actual logic