FS#76769 - [chromium] Build with Qt5 support

Attached to Project: Arch Linux
Opened by Emil (xexaxo) - Wednesday, 07 December 2022, 14:37 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 14 December 2022, 08:57 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Chromium 108 features a Qt5 backend, which can be used instead of the GTK3 one.

Our current maintainer Evangelos Foutras (hats off for all the amazing Arch work, bug reports and fixes that you've contributed upstream) is aware of that and deferring enablement to a later date [1].
May I ask why, can we enable it?

AFAICT the option is an explicit opt-in, so by default it will not change anything for the end-users.

Happy to do some testing, or otherwise, if that would help.

[1] https://github.com/archlinux/svntogit-packages/commit/4de5019014aeb77187a517c5ca6db8723d622a40


Additional info:
* package version(s)
chromium 108.0.5359.94-2

Steps to reproduce:
* install chromium
* open `chrome://settings/appearance`
* look for the Qt Theme
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 14 December 2022, 08:57 GMT
Reason for closing:  Implemented
Additional comments about closing:  chromium 108.0.5359.124-1
Comment by Ike Devolder (BlackEagle) - Wednesday, 07 December 2022, 14:59 GMT
IMO enabling qt at this moment is not really useful, depending on 2 UI frameworks is serious overkill since many parts of the chromium source code will still refer to GTK3 as well even with QT enabled.
Comment by Emil (xexaxo) - Thursday, 08 December 2022, 13:21 GMT
@BlackEagle thank you, I didn't know that. Do you have any references where GTK3 code is used/referenced instead of Qt one? Is there a tracker somewhere that one can keep an eye open?

More importantly - the qt5 dependency should be an optdepents, since by default it's not used nor required. Hence it won't be installed for people who don't want to use it.
Comment by Ike Devolder (BlackEagle) - Saturday, 10 December 2022, 18:18 GMT
I have tried to build chromium for fun a while back with QT only and that did not work, had to add gtk3 back to make it work, so therefore I thought at that time that it is not very usefull at the moment.
Comment by Emil (xexaxo) - Sunday, 11 December 2022, 20:45 GMT
Sounds like we're conflating two things:
- building with qt5 support, and
- building _without_ gtk3 support

I think the former makes sense to initiate now. The latter would be nice, but it's a non-goal for the time being.
Comment by Ike Devolder (BlackEagle) - Monday, 12 December 2022, 07:00 GMT
Thats why I don't find it really usefull at the moment, if you want to use qt, you still depend on gtk3 as well. I'm not a fan, but ok I see the point that you have to start somewhere to get to a potential future split package where one depends on gtk3 and the other on qt
Comment by Evangelos Foutras (foutrelis) - Wednesday, 14 December 2022, 08:57 GMT
chromium 108.0.5359.124-1 is built with use_qt=true (the default); to actually use it --enable-features=AllowQt is needed as well. (Chrome uses a finch experiment to launch it gradually I think.)

In the future it's possible that Gtk3 can be turned into an optdep (along with qt5-base) and Chromium should be able to use the appropriate toolkit based on the desktop environment it's launched in.

Loading...