Yes, we definitely want similar things. Maybe it was not clear from my original reply but I’m not saying the document paradigm is bad and we should move away fr

Yes, we definitely want similar things. Maybe it was not clear from my original reply but I’m not saying the document paradigm is bad and we should move away from it. The document paradigm has evolved for 25 years and it is the right fit for most “websites”. The problem is that we’re trying to build apps on the same base as well and that is where the mismatch is. If you look at cross platform GUI toolkits like Gtk, Qt, Flutter and Druid, what most of them have in common is that they are typically abstractions on top of a graphics rendering library (cairo, skia, canvas) with integration into platform accessibility and window APIs. That makes them easily portable to Linux, Windows, Android, iOS etc. The problem with the web browser as a target platform for these toolkits is that the accessibility support is currently coupled too tightly with dom/html/css. The graphics drawing toolkit is there (canvas) and most of the above toolkits have abstracted over it already. The missing link is standardised accessibility APIs in browsers that can be used with canvas instead of dom.