QtWebEngine

Let me know if you figured a way to make it work, currently stuck on this too. I must say the documentation is lacking on QWebEngine. The example is too complex for nothing, we don't want a chat server, just a simple WebPage communicating to C++ in both way (printing text and alert message example would be sufficient to understand). I don't understand why they use a QWebSocket since it's not necessary? Any more example around that could help? I did everything the docs says and I can't get it to work js-->c++, the other way is easy with runJavascript

Yes, I have seen that. One problem though is often finding the chromium resources, QtWebEngine will search for them in the Qt prefix paths, so if they are different than QtWebEngine's that can cause issue. QtWebEngine will also try several fallback until it gets to the directory of the executable. Here it is important to note that it is a multi-process architecture, and that besides your own executable also is an executable in libexec, that also needs to find some resources.

It is a known limitation. Pepper Flash for some odd reason use a completely separate fullscreen system than the rest of Blink or Chromium, and it integrates badly with QtWebEngine. If you have control over content, one thing you could probably do, is use HTML5 fullscreen mode to set the embed or object element fullscreen, instead of using the Flash fullscreen.

@d1.psy so you want the cookies from the requests you already made with QtWebEngine? If so take a look at QWebEngineCookieStore (see it's signals) and "sync" the cookies into your QNAM.

See https://bugreports.qt.io/browse/QTBUG-55542

I don't remember whether there's a plugin for Designer for QtWebEngine. However it should be pretty easy to set things by hand in the constructor of your object.

Okay, after four days of research, turns out the specific DLL - Qt5WebEngineCore.dll doesn't like being compressed by UPX. It's not noticeable immediately, but on approx. 10 % of PCs the QtWebEngineProcess simply crashes.

You can try the suggested solution here

Found the problem. It looks like during the initial stage of nmake, it was spitting out some errors complaining that the command line is too long. I found this ticket and patched those 3 files into my directory and it fixed the problem: https://codereview.qt-project.org/#/c/160622/ Later down the line I experienced another compile issue (https://bugreports.qt.io/browse/QTBUG-54455) and patching this file fixed it: https://codereview.qt-project.org/#/c/163955/

Hi and welcome to devnet, That's a question you should bring to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

@mousemao I've made a feature request here https://bugreports.qt.io/browse/QTBUG-55074 BTW, 大哥，你好~~