Interesting, since it makes me wonder if it could actually be usable if you stripped out Qt and flattened things "down" to a simpler widget set and rendering engine, but completely unusable on all my machines.
Longer-term, we need to move to browser-native GUI, yep. The nice bits though - the entire document loading, rendering & editing works in the browser now.
What that means though? A VCL backend that targets HMTL5 instead of Qt?
Can you elaborate?
We already use cairo/freetype/skia to do essentially all the document rendering in software (not for the Qt prototype though), so that's not a big leap to get that blitted out.
Incrementally then using more of html canvas to speed things up might be next.
Most of the work is going to be having the GUI (toolbar/notebook bar, menues, sidebar, dialogs) browser-native of course.