Fair but native <select> is also terrible. If we built web with only native components we'd never get a decent experience. That's my point. We shouldn't necessarily rely on people reimplementing. The browsers could do it but they have to try harder.
-
-
And frameworks use the non-isolated DOM as a substrate to building isolation paradigms on top. This is all fine but the style/event conflation set frameworks back years from using Shadow DOM for style isolation. Makes me sad.
-
There's a good thread where a member of the shadow dom team tried to explain why style isolation is coupled to DOM isolation. Let me try to dig that up...
-
https://github.com/whatwg/dom/issues/531#issuecomment-341609348 … I don't actually work on the rendering engine so I can't argue the validity of his point. But wanted to share the information.
-
Meh. Style isolation is nice but not the reason the web is trailing in UX.
-
I think you hit on it earlier. Exposing lower level APIs in a way that doesn't mess up the security sandbox is tricky. But folks are working on it, just maybe not as fast as we'd all like :)
-
In practice, the speed of the work is really slow and people can't ever help themselves from trying to avoid footguns at the same time. New primitives should expose the low level and leave ergonomics to libs using the primitives.
-
If you try to build ergonomic primitives you go slow and don't expose the needed stuff to frameworks anyway. Worst of both worlds.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.