-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QtWebKit needs to be deprecated #53079
Comments
I don't think we'll be able to kill the dependency easily in
|
Not unofficial – endorsed by Qt: https://code.qt.io/cgit/qt/qtwebkit.git/ And currently in the process of a massive overhaul thanks to Patreon funding. |
@KAMiKAZOW This is definitely a good news for qtwebkit and its users. However, we are using a specific 5.212-alpha version that is outdated and contains known CVE's. Looking at the repo at your link, it doesn't seem to contain any significant update to address those issues. I doubt anyone would endorse this software in its current state. |
The development happens here on Github. "My" link was solely a reference proving that it's not unofficial but instead adopted by upstream Qt. As you can read under https://github.com/qtwebkit/qtwebkit/blob/qtwebkit-dev/ReadMe.md#this-repository-development the qtwebkit-dev branch is the update to current WebKit master. |
zeal ported to qtwebengine (zealdocs/zeal#1125), not released yet. |
Freecad will be ported with the 0.19 release FreeCAD/FreeCAD@75fd723, not released yet |
messagelib no longer depends on qtwebengine since c2366ae |
The issue for OpenShot linked in the description is outdated; it's been superseded by OpenShot/openshot-qt#3604. |
example: scrapinghub/splash#349
|
p4v doesn't depend on qtwebkit since #110168. |
apitrace is done: #201032 |
|
See PR NixOS#201028 and issue NixOS#53079
@das-g How are you going with fixing the kmymoney build? I'm hitting build errors in my attempts to build against |
@aidalgol working on it, should be ready in some minutes. |
(to get rid of transitive dependency on qtwebkit) See PR NixOS#201028 and issue NixOS#53079
qgis depends on it and isn't in the main list. Looks like it can build with QtWebEngine but won't work due to some bugs, see qgis/QGIS@7c1d616 |
|
The suggested move to QuiteRSS2 (https://github.com/QuiteRSS/quiterss2) might make sense, since it uses QtWebEngine, but I'm unsure about any unwanted implications this could lead to. |
On the AUR (patches fetched from there) it has been unmaintained as well: I'd suggest changing the ✔︎ to a ✘ for its entry. |
|
Issue for a port from QtWebKit to QtWebEngine for |
Qtwebkit has been marked insecure since #201028. No point in trying to check every single box. |
Fantastic 😅 |
QtWebKit was deprecated in Qt 5.6. We are now using an outdated unofficial port:
nixpkgs/pkgs/development/libraries/qt-5/5.12/default.nix
Lines 40 to 49 in b0705bc
In some cases, applications already provide support for using QtWebEngine instead, we just need to enable it. The advantage of using QtWebEngine is that it is supported by the Qt upstream.
This issue is to track progress (or lack thereof) in deprecation of QtWebKit.
Overview
Legend: ✔︎ - dependency can be removed, ✘ - no straightforward solution was found, ? - dependency can be removed at a cost
qtwebengine
andqtwebkit
qtwebkit
optionallyHow to help?
The text was updated successfully, but these errors were encountered: