QtWebEngine

Do you have a solution for that problem? I need.

I dont get errors when i use gold linker but website’s dont load , i get blank screen.

@delamor hi, why build for x86_64 if targeting M1 machine ? There's a translation layer that will incur a performance hit.

hi！did you solve the problem, i met the same problem.

It's not related to Debug or Release. The error is caused by line endings. The parser expects unix instead of dos line endings.

Hi,

You can build the latest Qt 5.15 for your project and if it works better. If so backport the changes.

Hi,

You should move to PySide6. Support for OpenSSL 3 started with Qt 6. Even if the support is back-ported to 5.15, you would need to build PySide2 yourself with the corresponding version of Qt 5.

@CompSciDude
I tried -no-webengine-jumbo-build when building Qt 6.7.2, still cannot build cause by out of memory (12 G RAM). Neither --webengine-jumbo-build=<number>

Found the problem, I'm replying if someone else got the same problem.
I needed to put this line of code :

os.environ["QTWEBENGINE_CHROMIUM_FLAGS"] = "--no-sandbox"

And to use sys.argv when initializing the app :

App = Qt.QApplication(sys.argv)

The final code being the following :

import PyQt5.QtWidgets as Qt from PyQt5 import QtCore import PyQt5.QtWebEngineWidgets as QtWeb import sys import os class WebView(Qt.QMainWindow): def __init__(self): super().__init__() self.setWindowTitle("Web View") self.setGeometry(100, 100, 800, 600) self.webview = QtWeb.QWebEngineView(self) self.setCentralWidget(self.webview) self.webview.load(QtCore.QUrl("https://www.google.com")) if __name__ == "__main__": os.environ["QTWEBENGINE_CHROMIUM_FLAGS"] = "--no-sandbox" App = Qt.QApplication(sys.argv) window = WebView() window.show() app.exec_()

Hope it helps if someone gets the same issue !

If I keep the code posted above and if I modify my webBrowser function with this code

void MyMainWindow::webBrowser() { // Creation Objects m_webViewer = new QWebEngineView(); // Initialisation QString urlPage = "http://factice_url/simple_page.html"; // Setting and Loading URL (HTTP Object used because subsequently need to apply headers) QWebEngineHttpRequest httpObjet; httpObjet.setUrl(urlPage); m_webViewer->load(httpObjet); // Connexions connect(m_webViewer,&QWebEngineView::loadStarted,this,&MyMainWindow::manageBeginLoading); connect(m_webViewer,&QWebEngineView::loadFinished,this,&MyMainWindow::manageEndLoading); }

And if I add this function

void MyMainWindow::manageBeginLoading() { // Set Central Frame setCentralWidget(m_webViewer); }

Application works in mode Debug and in mode Release without problem.
With this changes I move setCentralWidget(m_webViewer) into the function launched when signal loadStarted is emitted.

But is this correct or should we deport the creation of the m_webViewer and the connections in the constructor..?

I have already solved this problem. The solution is:

m_view->settings()->setAttribute(QWebEngineSettings::LocalContentCanAccessRemoteUrls, true);

Hello!

So, I added this patch: https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/505412
I have successfully built QtWebEngine 5.15.14 for Visual Studio 2022. Now, this issue is resolved.