@JKSH Thanks a lot for your answer!!! This question bugged me for days.

Very embarassing but I found out I have to to build in RELEASE mode to have the full GPU acceleration. In practice that means doing cmake -DCMAKE_BUILD_TYPE=Release .. Then run windeployqt again. There should be QWebEngineProcess.exe - if there is QWebEngineProcessd.exe (the d for "debug") that means it is still in debug mode and will be slow.

@Johnsonq said in Qt6 QWebEngine Plotly js: Uncaught Error : Something went wrong with axis scaling: I.m using Qt 6.6.3, VS 2022, python 311 to plot something like 3D image. When I create QWebEngineView object like ui.setupUi(this); webEnginePlot = new QWebEngineView(tabPlot); webEnginePlot->setObjectName("webEnginePlot"); webEnginePlot->setUrl(QUrl(QString::fromUtf8("about:blank"))); MainWindow include [ MenuBar ] [QDockWidget QStackedWidget] QDockWidget on the left, QStackedWidget on the right. QDockWidget include QTreeView, QStackedWidget include QWebEngine Question 1: Why the whole surface flashing(or hide, or white screen) 1 or 2 seconds? I found out it is loading QtWebEngineProcessd.exe When I try to new QWebEngineView() before QTreeView init, nothing wrong. And when I init QTreeView first, then new QWebEngineView(), and the whole soft began to flashing(or hide, or white screen) to loading the QtWebEngineProcessd; Question 2: I use C++ PythonAPI to draw a plot using plotly, and come out a file like a.html, and then I load the html file with QWebEngineView, and it showed up "js: Uncaught Error: Something went wrong with axis scaling" QUrl localUrl = QUrl::fromLocalFile(htmlFile); ui.webEnginePlot->setUrl(localUrl); ui.webEnginePlot->show(); But when I enter the QWidget and click my button to draw it again, and it works. Why when initializing, it will report an error？ How to solve the problem. Help me please! The flashing or white screen issue when initializing QWebEngineView is likely due to the time it takes to load the QtWebEngineProcessd.exe. To avoid this, try initializing QWebEngineView before the QTreeView, as you’ve noticed it prevents the flashing. For the axis scaling error when loading the plotly HTML file, this might be due to the JavaScript not fully executing during the initial load. To resolve this, ensure that the HTML and its resources are fully loaded before rendering. You can also try reloading the page after a short delay or implement a callback function to reattempt drawing after the first load.

I think I found the issue - it was because I the app uses a tray icon and WM_CLOSE doesn't fully close the app. This appears to play badly with the Windows restart manager. The solution was to use a custom script to terminate the app during update / removal.

@somethingvague I'm also having the same problem with my application. In my case I initialize the class which contains the web engine view instance (let us say class B) after someone clicks some button in a different class(let's say A), Now both classes A and B have different UI interfaces. Can you please help me stop flicker from happening in this case? [image: 2c295871-744e-45db-8ff9-25e519eb770b.png] [image: fb00c9fd-87ef-469a-85bf-7af55e1cfc8a.png] I have shown the Class B initialization and engine setup above. I have initialized class and enigine setup before window.show() as been told in the above conversation.

Bonsoir, Non, de plus sur Android et iOS, ce sont les composants systèmes qui sont utilisés.

Issue is resolved. I had updated my GPU drivers and after restart, it began to work.

@Asif-QtAddict Oh! Well I have no idea why a 64-bit Chromium should behave any differently from a 32-bit one. If all it is is that it happens to be faster, presumably the problem will re-arise when the operation takes longer. Who knows!

First off, thanks for your time. I've tried that yeah - you can see that I've made the default index_file "qrc:/index-light.html" in the load_args function. It's here in the code. When writing to qDebug() the string is correctly "qrc:/index-light.html", though nothing is shown in the webview... I've tried changing it to "qrc:/light.css" and then it correctly shows the css in the webview (the code in plaintext).

oh my god! I can't believe i was so blind! Thanks a lot to both! I switched the connection back to QWebEngineView. I don't even remember why I thought that sending the signal from QWebEnginePage was a good idea, since i have to delete the pointer not to let it hanging. Now it seems to work, but pix comes out blank. Perhaps loadfinished is too quick, and triggers before javascript has finished generating the document? Is there a slower signal? Or perhaps a way to give js a tad more of time to load before calling render? Before using signals and slots I tried to wait it with a loop, but it seems the loop blocks js.

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 :)

Ok so I managed to import the html by modeling my code similar to the example with: QString code = QStringLiteral("qt.jQuery('#first_page').load('html/first_page.html');"); //you can even nest it with: QString code = QStringLiteral( "qt.jQuery('#first_page').load('html/first_page.html', ()=>{" "qt.jQuery('#border_content').load('html/border_content.html', ()=>{" //some other html "qt.jQuery('#last_page').load('html/last_page.html');" "});" "});" ); unfortunately I now cannot use the qwebchannel.js script anymore and my css gets screwed :( even loading it with: QFile script_file(":/qtwebchannel/qwebchannel.js"); if(!script_file.open(QIODevice::ReadOnly)) qDebug()<<"Couldn't load Qt's QWebChannel API!"; QString qt_script = QString::fromLatin1(script_file.readAll()); script_file.close(); view->page()->runJavaScript(qt_script); did not help. Since it is a small project and I am on a short deadline right now I will put everything in one html file and mark this question als solved.

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

I've decided to report this issue as a bug here. Was you able to reproduce the issue ?

@dheerendra said in QWebEngineView doesn't work with paid proxy.: Since authentication is required, did you catch the signal proxyAuthenticationRequired from webEngine page ? I know now, that i have to use connect method to catch this signal, but i don't know, what do i have to do after.