Not to diminish what you're saying because I agree with you, but I'm less upset about malicious site operators (they could always have been doing this even before WebASM) and more concerned about the beginner (or advanced) programmer that's looking at this thinking, "sweet, I can write my app in Qt, hit an export button, and everything will magically just be fine."
Honestly, I'm not even upset at that developer - they should be able to just hit a button and have it magically work.
I'm upset that Qt isn't rendering any of their stuff to the DOM. CSS is good enough to handle this nowadays, it can't possibly be easier to write their own rendering engine from scratch than it would be to just use the tools that are already built into every browser.
They should be using Canvas only as a fallback when nothing else will work.
Also I hate the totally inconsistent look of the components we do have. I mean anything I make on linux or windows is close to intolerable on mac. Which is, of course, why all designers totally avoid them and instead just totally redesign everything from scrollbars to buttons.
The web is ... decent ... for what are essentially slide handouts ("websites"). Let's start making some real applications now.
Not only do we need to deal with rendering to the DOM, we need to hack their rendering code when CSS issues pop up across browsers.
Did you know that the original rendering engine of webkit & blink, khtml, was Qt's ? Besides, the platform abstraction that allows to use Qt on top of WASM is less than 3k lines of code - everything else is the same whether you're on windows, mac, whatever.