QtWebEngine

I report this issue to official and but them not yet solved, you can vote it. My solution is automatically zoom in webpage when the dpi is high. https://bugreports.qt.io/browse/QTBUG-53449

That's a Known Issue, qt official will fix it in qt 5.7rc version. https://bugreports.qt.io/browse/QTBUG-52517?filter=17619

Solved: the cause was the stub in mesa3d drm backend. It's solved by altering the backend.

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

@eureka And if this doesn't work you could use something like pdf.js (https://mozilla.github.io/pdf.js/)

I opened a bug report: https://bugreports.qt.io/browse/QTBUG-53042

Please mark as [SOLVED]

Did you ever find a solution so that you don't have to call a function that then emits a signal? I am running into this problem as well and we have several functions. The closest I've found are examples that only show how to connect a javascript function to a c++ signal.

@professorkaos64 I had a look at the OpenSUSE 5.6 spec file for this. My other attempt at bulding qtwebchannel into a proper set of install files tried to mimic this. If I don't provid install files, everything get's installed to /lib and /include, not /usr/lib... and /usr/include/.... which seemed strange since the prefix is usr/ for my qtbase install and all other modules built fine. What part of that spec file is the binary I can double check? Where should qtwebchannel be installing? I know my catch all package installs the headers, but what piece of that install spec denotes the binary for me to check that it built? I'm sorry but I really can't say, I have no idea what that file is or how it's used. It looks like a shell script, but I don't recognize the interpreter. That said, I'd first look at the chrooted /usr/lib (or /lib) if the Qt5WebChannel.so is present, if not it should somehow be made available to the linker, either by providing a symbolic link to it's location or by copying the binary from it's build location. I'm sorry I can't be more specific, but I reiterate I haven't built anything this way, and only observed that there's no build step for said module. PS. I'm sorry for the delay, I was pretty busy these two days.

Loading should work this way, if you use the correct file format QSslSocket::addDefaultCaCertificates(certdata.pem) Look here: https://curl.haxx.se/docs/caextract.html You also need SSL error handling - use this as a working base: connect(webGUI->page()->networkAccessManager(), SIGNAL(sslErrors(QNetworkReply*, const QList<QSslError> & )), this, SLOT(HandleGUIsslErrors(QNetworkReply*, const QList<QSslError> & ))); void QTGUI_MainWindow::HandleGUIsslErrors(QNetworkReply* reply, const QList<QSslError> &errors) { foreach (QSslError e, errors) { qDebug() << "GUI SSL error:" << e; QByteArray qbTemp; qbTemp.append(e.errorString()); } //reply->ignoreSslErrors(); // this is only a hack !! reply->abort(); } HTH