Yes I was using a busy loop calling QApplication::processEvents(); once in a while
Yes you can run QtWebEngine headless/in console but it requires QApplication and won't work with QCoreApplicaion
Much alike WebKit it requires quite frequently access to main event loop i.e. do not block it for extensive periods of time
I need to investigate... any pointers, documentation...
but note that these are still under development and the behavior may be erratic.
To follow this development you can ask the question on "Interest Mailing List":http://lists.qt-project.org/mailman/listinfo/interest, you might get an answer directly from the Qt developers. You will need to subscribe to the list first.
Well, that does indeed look like roughly what I had in mind, though it seems to be in a very immature state. Still, I won't work on it myself, since I don't have much interest in web technology. Furthermore, I don't think this will ever yield satisfactory performance.
Let me just add that if you right-click in a Chrome browser window, the context menu is quite different depending on whether you right-click on a link ("Open Link in New Tab," etc), on an image ("Save Image as..." etc), on open text ("Back", "Reload" etc), even different again on an image that is inside a link.
So the browser code itself certainly has all the details of the target under a right-click. With QWebPage that information is available. I hope that it is available from QWebEnginePage and that I have just overlooked it.