Public bug reported:
In https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1837746,
it's suggested that passing chromium flags `--AAA=BBB` by writing
`CHROMIUM_FLAGS=--AAA=BBB` to ~/.chromium-browser.init
However, if AAA is disable-features, ie. `CHROMIUM_FLAGS=--disable-
features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled`,
this does not work.
The launcher script concatencates the CHROMIUM_FLAGS:
`CHROMIUM_FLAGS="$CHROMIUM_FLAGS --disable-
features=TFLiteLanguageDetectionEnabled"`
as a result, the later disable-features, TFLiteLanguageDetectionEnabled,
overrides the former one,
ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122562
Title:
disable-features flags does not work in chromium-browser.init
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2122562/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
