Qt WebKit

The default compilation settings of QtWebkit (in Qt5.5 ) generates strip down version of qtwebkit which does not include DRT. In order to get DRT goto <path to qt5 source code>/qt5/qtwebkit/Tools/qmake/mkspecs/features/configure.prf and comment the following line. (Note ## is used for comment.) production_build { ## WEBKIT_CONFIG -= $$WEBKIT_TOOLS_CONFIG build_tests } First clean any previous configuration: $ git submodule foreach --recursive "git clean -dfx" Configure: $ ./configure -opensource -confirm-license -release Build webkit only: $ make module-qtwebkit Install: $sudo make install You will find DumpRenderTree executable in <path to qt5 source code>/qt5/qtwebkit/bin Set environment variable $ export WEBKIT_TESTFONTS=<path to qt5 source code>/qt5/qtwebkit/Tools/DumpRenderTree/gtk/fonts Run $ cd <path to qt5 source code>/qt5/qtwebkit/bin $ ./DumpRenderTree http://www.xyz.com

@MtDewQt qputenv("QTWEBKIT_PLUGIN_PATH","C:\Windows\SysWow64\Macromed\Flash");

Out of curiosity, why not use the system installed Qt ?

When you load libraries ...(html code): <script src="http://... instead <script src="https://...

Work perfectly. Thank you very much.

@coquetangler this is a community driven forum so there might be very well only a few people using webkit and being able to help. However the bug report system is available to double check. The interest mailing list is also a good place to talk about that kind of cases.

@coquetangler This is a community driven forum, so there might not be that many users of QtWebKit here, however there's also the bug report system as well as the interest mailing list where you can find Qt's developers/maintainers that can be consulted about that kind of matters

@coquetangler Hi, this forum is community driven so it's probably something that none of the users here could answer. In any case, you can follow the progress of the fix on the bug report and gerrit patch (see last post on the bug)

The only solution us to go back to Qt 4.8. Qt 5 is a mess.

This is a known bug inside WebKit that was reported a long time ago and still has not been fixed. It's to do with rendering sub frames. There have been various lame attempts to fix it but it was not. The only solution is to revert back to Qt 4.8 which does not have this issue. It's unfortunate that nobody seems to be maintaining QtWebkit anymore when it's such an important component of Qt. QtWebEngine is totally lacking with no simple integration with Qt and the restriction that all calls are async. What a mess.

Hi, You have the ICS Qt based google APIs clients As for licensing, you should ask Google directly

I found a bug from 2009 about the same problem: https://code.google.com/p/chromium/issues/detail?id=13175

Great, it worked perfectly. Thank you very much for your help!