WebKit Status 2017
Welcome to the forum:
Starting from Qt 5.6 release the WebKit classes are removed from official binary distribution of Qt.
(Removed Modules section)
However, each Qt release has corresponding QtWebKit sources that are available at
Linux distributions and other package systems usually provide binary packages for QtWebKit
based on these sources so you can install QtWebKit module just like you could do it before.
You can also build them yourself
"official" QtWebKit releases
But that is not the easy route for beginners.
The alternative is to use
However, when webengine is not an option, there is the QtWebKit reboot project
providing prebuilt packages
A few comments:
- First and foremost: you should not use version released with Qt (http://download.qt.io/community_releases) in any applications that allow user to do web surfing on untrusted content. QtWebKit releases corresponding to Qt 5.2 - 5.9 are based on WebKit branch from 2013 and have lots of unfixed security vulnerabilities. To the contrast, QtWebKit at https://github.com/annulen/webkit is based on branch from 2016
- You can use official sources from qt.io in case
you need QML API (not yet finished in my branch), orif you cannot use updated QtWebKit because of changed system requirements. There are probably no other valid reasons to do that, and keep in mind warning above.
- Note that documentation of QtWebKit is available online at http://doc.qt.io/archives/qt-5.5/qtwebkit-index.html, it is relevant for Qt 5.6 and all newer versions
In any case, it is a bad idea to continue using Qt 5.5.1 because of QtWebKit. You should update to latest stable (or LTS) Qt version, and use QtWebKit from https://github.com/annulen/webkit/releases, or in case it is not suitable for some reason, from http://download.qt.io/community_releases. Please contact me if you if something is preventing you from using QtWebKit TP5 besides reasons that were listed above.
UPD QML API is supported since QtWebKit 5.212.0-alpha
Feature-wise comparison of QtWebKit reboot with official sources:
Note that we are very close to feature parity now, i.e. there are very little features that work with legacy QtWebKit and are not yet supported with reboot, and their number is constantly lowering.