3 ms·

While the Chromium version in QtWebEngine only gets updated for major releases (all ~6 months), they do backport security fixes. The latest 5.11.2 release comes

While the Chromium version in QtWebEngine only gets updated for major releases (all ~6 months), they do backport security fixes. The latest 5.11.2 release comes[1] with fixes up to Chromium 68.0.3440.75, and the upcoming 5.12 release (scheduled[2] for November) updates[3] the baseline to Chromium 69. It's a bigger issue if you're on a distribution like Debian Stable, which ships an ancient Qt version without security updates[4]. There, you get Qt 5.7.1 based on Chromium 49 (2016-03-02) with security fixes up to 54 (2016-10-19)... I'll probably drop support for that soon even if it's annoying for some Debian Stable users, but people really should stop using such old QtWebEngine versions. Missing web features usually isn't much of a problem in my experience, as most sites still wait a bit before they start using them. FWIW I agree something based on Servo would be cool, and as soon as there's some project making Servo embeddable from Python with Qt integration, I'll get my hands dirty to at least have a proof of concept! [1] http://code.qt.io/cgit/qt/qtwebengine.git/tree/dist/changes-5.11.2/?h=v5.11.2 http://code.qt.io/cgit/qt/qtwebengine.git/tree/dist/changes-... [2] https://wiki.qt.io/Qt_5.12_Release https://wiki.qt.io/Qt_5.12_Release [3] http://code.qt.io/cgit/qt/qtwebengine.git/tree/tools/scripts/version_resolver.py?h=5.12#n41 http://code.qt.io/cgit/qt/qtwebengine.git/tree/tools/scripts... [4] https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#browser-security https://www.debian.org/releases/stable/amd64/release-notes/c... - only mentions QtWebKit, but applies to QtWebEngine too

rjzzleep 8y ago
Considering that 5.12 is an LTS release, they are evaluating to separate WebEngine from the normal QT release cycle. > This is still under research, but there seem to be quite tangible benefits from carving out Qt WebEngine to a separate item. Current thinking it that as a separate item we should be able to release Qt WebEngine every three months, following nicely the schedule of Chromium releases every six weeks. For Qt 5.12 LTS users this would mean the possibility to get not only the security updates, but a full new Chromium version supported on top of the long-term-supported release of Qt. https://blog.qt.io/blog/2018/02/22/qt-roadmap-2018/ https://blog.qt.io/blog/2018/02/22/qt-roadmap-2018/
- The-Compiler 8y ago
  I doubt that'll happen with Qt 5.12, but it hopefully will with Qt 6: https://bugreports.qt.io/browse/QTBUG-63235 https://bugreports.qt.io/browse/QTBUG-63235

rjzzleep 8y ago

Considering that 5.12 is an LTS release, they are evaluating to separate WebEngine from the normal QT release cycle. > This is still under research, but there seem to be quite tangible benefits from carving out Qt WebEngine to a separate item. Current thinking it that as a separate item we should be able to release Qt WebEngine every three months, following nicely the schedule of Chromium releases every six weeks. For Qt 5.12 LTS users this would mean the possibility to get not only the security updates, but a full new Chromium version supported on top of the long-term-supported release of Qt. https://blog.qt.io/blog/2018/02/22/qt-roadmap-2018/ https://blog.qt.io/blog/2018/02/22/qt-roadmap-2018/

The-Compiler 8y ago
I doubt that'll happen with Qt 5.12, but it hopefully will with Qt 6: https://bugreports.qt.io/browse/QTBUG-63235 https://bugreports.qt.io/browse/QTBUG-63235