Hi Dmitry! Dmitry Shachnev <mity...@debian.org> writes:
> Hi everyone! > > Sorry for the late reply, but let me try to answer the questions which remain > unanswered. Thank you for finding the time to reply and to explain the Qt side of things :) > On Sun, Oct 29, 2023 at 07:43:51PM +0100, Alexis Murzeau wrote: [snip background] > >> Qt 6 doesn't seem to have Qt webkit anymore, but QtWebEngine instead. >> I guess signon-ui should move to QtWebEngine instead but sadly upstream >> seems rather dead :(, the previous signon-ui release was more than 5 >> years ago. > > Yes, Qt WebKit does not support Qt 6, so the only choice is to migrate to > Qt WebEngine which is supported much better. I would recommend doing that > even if you stay on Qt 5. I've filed #1055855 for this purpose, with a link to a breadcrumb trail from SUSE. > Unlike Qt WebKit which is based on Apple WebKit, Qt WebEngine is based on > Chromium codebase. > > Qt WebEngine user agents will look the following: > > Qt 5.15: > Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) > QtWebEngine/5.15.15 Chrome/87.0.4280.144 Safari/537.36 So if we backport signon-ui's future Webkit -> WebEngine fix to bookworm, Google might still blacklist bookworm kaccounts users for having a user agent string that advertises an ancient browser? Chrome/87.0.4280.144 is pretty old. That said, I assume there are security reasons why we should use WebEngine and not Webkit in bookworm? Kind regards, Nicholas
signature.asc
Description: PGP signature