4 ms·
There's also Falkon, now a KDE project, which I prefer. The UI is more like Firefox, and it's QtWebEngine-only, which is maintained, unlike QtWebKit these days.
by abrowne 8y ago
There's also Falkon, now a KDE project, which I prefer. The UI is more like Firefox, and it's QtWebEngine-only, which is maintained, unlike QtWebKit these days.
https://www.falkon.org/ https://www.falkon.org/
- kodablah 8y ago> maintained, unlike QtWebKit these days Seems somewhat revived/maintained by annulen [0] as pointed out in these release notes. Also, QtWebEngine seems to usually be behind a Chromium version or two which, among other reasons, is why I use CEF in my Qt-based browser (granted I'm behind a couple versions on public releases, but that's my fault). 0 - https://github.com/annulen/webkit/tree/master https://github.com/annulen/webkit/tree/master
- abrowne 8y agoYes, that QtWebKit revival is interesting and worth watching. I haven't followed, but I'm still not sure if it's up-to-date. This blog post from a WebKitGTK+ (with a section about QtWebKit) developer from 2017 is the best info I could find: https://blogs.gnome.org/mcatanzaro/2017/08/06/endgame-for-webkit-woes/ https://blogs.gnome.org/mcatanzaro/2017/08/06/endgame-for-we... And yes, QtWebEngine does not keep up with Chromium, but it is updated to some degree. I wish Qt and distros could at least keep better up-to-date with security fixes, but it's easier said than done!