2 ms·

> but sadly even the qt5-webengine backend is stuck back in Chromium 65.X which was released at the very beginning of this year Good shout, I did not realise t

by tomxor 8y ago

> but sadly even the qt5-webengine backend is stuck back in Chromium 65.X which was released at the very beginning of this year Good shout, I did not realise this, however the last release (5.11.2) was relatively recently in June... however I can't find release details for qtwebengine, where are you getting your release information from RE chromium? This was the main reason I was attracted to this browser because the old webkit2 based vim-like browsers were hopelessly out of date to point of being very dangerous.

igneo676 8y ago
Yeah, they don't call out what version they're on without some digging. I had to actually download the browser and check manually > This was the main reason I was attracted to this browser because the old webkit2 based vim-like browsers were hopelessly out of date to point of being very dangerous. Same here. I had to forgo other browsers I quite like because of their older versions of webkit
- tomxor 8y ago
  If the user-agent string is to be trusted the latest version released in June is still based on chrome 65.x like you said... :/ it's not terrible but not great either. However they do claim to backport security patches on their front page so it should technically be secure. I suppose it would take a lot of repetetive effort going through the same process to pull apart chromium each major release, so perhaps they settle on backporting patches in between larger breaks.
  - The-Compiler 8y ago
    Yeah, I recall them saying they need something like two man-months for each Chromium release to adapt (the changed lines in the imported Chromium source is usually somewhere around a couple of million...).
    - tomxor 8y ago
      > the changed lines in the imported Chromium source is usually somewhere around a couple of million. Yeah that sounds truly horrifying, I guess they must employ some degree of automation though.
The-Compiler 8y ago
It's in their documentation (but a bit hidden): http://doc.qt.io/qt-5/qtwebengine-overview.html#qt-webengine-core-module http://doc.qt.io/qt-5/qtwebengine-overview.html#qt-webengine... (This version of Qt WebEngine is based on Chromium version ...). I usually check their script, which also lets you switch between versions easily: 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... And I also have an overview here: https://github.com/qutebrowser/qutebrowser/blob/master/qutebrowser/utils/version.py#L309 https://github.com/qutebrowser/qutebrowser/blob/master/quteb...

by tomxor 8y ago

igneo676 8y ago

Yeah, they don't call out what version they're on without some digging. I had to actually download the browser and check manually > This was the main reason I was attracted to this browser because the old webkit2 based vim-like browsers were hopelessly out of date to point of being very dangerous. Same here. I had to forgo other browsers I quite like because of their older versions of webkit

tomxor 8y ago
If the user-agent string is to be trusted the latest version released in June is still based on chrome 65.x like you said... :/ it's not terrible but not great either. However they do claim to backport security patches on their front page so it should technically be secure. I suppose it would take a lot of repetetive effort going through the same process to pull apart chromium each major release, so perhaps they settle on backporting patches in between larger breaks.
- The-Compiler 8y ago
  Yeah, I recall them saying they need something like two man-months for each Chromium release to adapt (the changed lines in the imported Chromium source is usually somewhere around a couple of million...).
  - tomxor 8y ago
    > the changed lines in the imported Chromium source is usually somewhere around a couple of million. Yeah that sounds truly horrifying, I guess they must employ some degree of automation though.

The-Compiler 8y ago

It's in their documentation (but a bit hidden): http://doc.qt.io/qt-5/qtwebengine-overview.html#qt-webengine-core-module http://doc.qt.io/qt-5/qtwebengine-overview.html#qt-webengine... (This version of Qt WebEngine is based on Chromium version ...). I usually check their script, which also lets you switch between versions easily: 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... And I also have an overview here: https://github.com/qutebrowser/qutebrowser/blob/master/qutebrowser/utils/version.py#L309 https://github.com/qutebrowser/qutebrowser/blob/master/quteb...