Qt WebKit

@Vbrg So in a word Qt only offers integrated browser with chromium/Qt web engine.

@Aman55 What error? The messages you show in your first post when debugging? There is no error. For me they did not appear when I used Qt5 under Ubuntu 22.04 but all appear when I moved to Qt6 under Ubuntu 24.04. Very irritating. I raised the issue at https://askubuntu.com/questions/1526550/ubuntu-24-04-gdb-gnu-debugaltlink-missing-file-messages. No resolution, it's a change in gdb behaviour.

If you see a blank screen in QWebView, check that the URL is correct and fully qualified. Consider switching to QWebEngineView for newer Qt versions. Ensure you have the necessary WebKit or WebEngine dependencies, enable JavaScript if needed, and check the console for errors like missing resources or SSL issues. You can also try loading simple HTML to test. Updating Qt may fix any bugs causing the problem.

Since gcc13 was not yet out when Qt4.8.7 was released some now stricter c++ requirements are in place. you have to fix them by yourself. There error message is clear here - you need a virtual dtor - add it.

Hi and welcome to devnet, Are you thinking about the WASM platform ?

Yes, absolutely.

@elahav said in Anyone interested in resurrecting QtWebKit?: Unfortunately it is based on a version of WebKit that is considered old and riddled with security holes. This is not really true. It's master branch is currently based on WebKit upstream from 2023/12/18, which is quite in line with current WebKitGTK 2.44.x (though it may lack a few bug- and security fixes to be backported)

As I understand it, you visit a particular web page and get a JS error in an old browser. These things happen. The error means localStorage is not defined. If you try visiting that page via QWebEngine do you get that error?

@LS-KS said in Real Time Applications in Qt: Is there a way in Qt Framework to bind a cpu core to a Thread I don't think there is. You will have to use system calls to do this.

@jsulm Thankyou so much

@redstoneleo Just be aware/for anyone reading this: Your solution is doubtless useful/correct, but it is for QWebEngine. This thread is from a decade ago when that did not exist and is for QWebView, a different Qt web viewer engine which no longer exists/is supported.

@anshah it is simple, just ignore ssl errors and continue

@anshah all the ones listed under the Signals part of the class documentation. Crash ? I thought you only had an error.

@Babitha said in How to avoid vulnerabilities issues in wkhtmltopdf build by using patched qt 4.8.7: How to avoid this Since Qt 4 is out of support since ages the only way is to fix it by yourself or find someone who you can pay for.

thank you for suggest。i will try later。