FS#71288 - community/vivaldi: Add "vivaldi-flags.conf" to match "chromium-flags.conf"
Attached to Project:
Community Packages
Opened by Tomas Sandven (Hubro) - Friday, 18 June 2021, 14:06 GMT
Last edited by Ike Devolder (BlackEagle) - Monday, 24 January 2022, 19:34 GMT
Opened by Tomas Sandven (Hubro) - Friday, 18 June 2021, 14:06 GMT
Last edited by Ike Devolder (BlackEagle) - Monday, 24 January 2022, 19:34 GMT
|
Details
The Vivaldi browser is based on Chromium and supports most
(if not all?) of the same flags.
Any time the Vivaldi browser updates, which is fairly often, I manually edit the .desktop file to add the flags required to launch Vivaldi as a Wayland client. For Chrome, Chrome Dev and Chromium, this is *much* less of a pain, since they have chrome-flags.conf, chrome-dev-flags.conf and chromium-flags.conf, respectively. https://wiki.archlinux.org/title/Chromium#Making_flags_persistent These flag files are Arch-specific additions to the browsers. Would it make sense to also add a "vivaldi-flags.conf" to persist flags passed to the Vivaldi browser? |
This task depends upon
Closed by Ike Devolder (BlackEagle)
Monday, 24 January 2022, 19:34 GMT
Reason for closing: Implemented
Additional comments about closing: vivaldi 5.0.2497.48-2
Monday, 24 January 2022, 19:34 GMT
Reason for closing: Implemented
Additional comments about closing: vivaldi 5.0.2497.48-2
will be avaialble from vivaldi 5.0.2497.48-2