Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Feature Request
Category Packages
Status Assigned
Assigned To Ike Devolder (BlackEagle)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 5
Private No

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

Comment by Juan Simón (j1simon) - Saturday, 20 November 2021, 15:03 GMT
+1

Loading...