The status quo is that both browsers and JS ecosystem are doing a poor job. The JS ecosystem often has an excuse because we don't have access to the primitives that are needed. That's not to say that it would be good even if we did. The game theory might not align.
-
-
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 -
-
-
Didn't SD come about as a way of emulating/making public how browsers implemented some things (like video controls) internally?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.