Hi, Because of chromium minimal compiler requirements. Nothing Qt can do about. Either use an older version or update your compiler to VS 2019 which is backward compatible with VS2017 and has less bugs.

https://stackoverflow.com/questions/58875159/how-to-ignore-ssl-certificate-errors-with-qwebengineview link helped me to resolve the issue. Now HTTPS page load after ignoring ssl warning is fine. Thanks for ideas :)

I finally found the problème from qt documentation. My solution is to add : QTQUICK_COMPILER_SKIPPED_RESOURCES += testgooglemapwebengine.qrc in my .pro file.

@LovelyGrace said in webenginewidgets on .pro of library produce error: but when I am trying to build the whole project from sub dir project including the library and the console, it produce the error You need to add Qt += webenginewidgets to your console project as well.

I use QCoreApplication::setAttribute(Qt::AA_UseOpenGLES); It can really screen bugs。but , error too;

@pmh4514 I received an answer from Qt support, it solved the problem. Their answer below: On a virtual machine the OpenGL support might not be enough for rendering Qt WebEngine, so the quickest way to check if this is the case here is to do: set QT_OPENGL=angle on the command line or add: QGuiApplication::setAttribute(Qt::AA_UseOpenGLES); before the creation of the application object

@mpergand you are right, this line solved the problem. Thank you very much!

@allenck ahh, yes that would do it. It can tell Qt to look from plugins in other places. http://doc.qt.io/qt-5/qt-conf.html Good catch :)

Ok this put me in the right direction, having subclassed both the view and page, and using createWindow and acceptNavigationRequest, I see how this all works now.. Thanks!

@mrjj Thanks. I knows that. But I want know is there any approach to solve this in qtwebengine. Such as adding some plugins?

@Hans-Dijkema I have yet to try Qt 5.7 beta, but... it seems to me like you haven't installed QtWebEngine?...

Did you install MSVC2015 before or after Qt ? Can you see it in the Compilers tab ?

@Matty I'm running into this now. Were you able to find a solution?

@ThatDud3 well, Qt 5.5 have been released, but I don't see nothing about proxy in QWebEngineSettings XD It is real problem...

Hi, After 3 years... Anyway switching from debug to release compiler solved the problem for me.