QtWebEngine

@TonyN Can you provide a working code to do that?

After years of not getting an answer to my question, I finally managed to resolve the matter myself. So for all the folks out there facing the same issue, the solution is as simple as dumb: You need to compile everything on a 32-Bit host! As a matter of fact, the QTWebEngine build system somehow is tailored for 32-Bit compilation. Simply installing the multi-arch packages on a 64-Bit system is not sufficient enough, it really needs to be a 32-Bit machine. In my case, I successfully built QT5.15.2 under Debian Stretch 9.13 32-Bit without any issues. I consider this case closed.

Hmm, migrated to 5.15.2 from 5.15.0 and it started to work .. both used MSVC2019_64bit .. not really sure what happened but I'm moving forward now. Thanks.

@JonB found it, looks like I was changing directory during core computing and webengineview could not find the .dll anymore but somehow did not complain about that. Thanks for all support I am just wondering if qwebengineview should not emit a warning or something when .dll not found...

@dscyw I'm facing the same issue. Have you found a solution?

@AI_Messiah You need to install OpenSSL support.

Reverted to 5.12.2 Everything is now working again. Not sure what the issue is/was.

There is a non-existent variable referenced somewhere. This variable needs to be declared, or you need to make sure it is available in your current script or scope otherwise , it will endup throwing this 'x' is not defined error . This usually indicates that your library is not loaded and JavaScript does not recognize the 'x'. To solve this error: Load your library at the beginning of all your scripts. There can be multiple other reasons for this issue: Added JavaScript library after the script were you see that error Conflict with Other JavaScript Libraries Path to JavaScript library you included is not correct The jQuery library file is corrupted May be a chance where you are working offline

There's a line in the error log with... "source: https://" Are you browsing to a secure webpage? Do you have SSL installed? if ( QSslSocket::supportsSsl() ) { qDebug() << "SSL support found" ; qDebug() << "SSL lib build: " << QSslSocket::sslLibraryBuildVersionString(); qDebug() << "SSL lib version: " << QSslSocket::sslLibraryVersionString() ; } else qDebug() << "SSL support NOT found" ;

Temporarily use QWebEngineDownloadItem to achieve download

@ppmm any other webengine flags can also be set via an env variable, also described on the link i've posted... Beside that: you can pass these parameters as simple arguments to the calling application. QtWebEngine gets the parameters from the QApplication instance (which should anyway get the parameters in the main() function normally) Regarding the blank page: What Desktop Chrome version are you using? Since v80 onwards you may want to start an instance with the following parameter: chrome.exe --enable-blink-features=ShadowDOMV0,CustomElementsV0 Hint: If you try to debug from a different machine you may rather want to set it to: QTWEBENGINE_REMOTE_DEBUGGING=0.0.0.0:1050

I made a little mistake. This CSS code in my html file caused this problem. @page { size: 8.27in 11.69in; margin: 0.86in; }