Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable and enable flags #3126

Open
3 tasks
carlosfmesilva opened this issue Dec 17, 2024 · 2 comments
Open
3 tasks

Disable and enable flags #3126

carlosfmesilva opened this issue Dec 17, 2024 · 2 comments
Labels

Comments

@carlosfmesilva
Copy link

carlosfmesilva commented Dec 17, 2024

OS/Platform

Debian, Ubuntu, and derivatives

Installed

https://ungoogled-software.github.io/ungoogled-chromium-binaries/

Version

Version 131.0.6778.139 (Official Build, ungoogled-chromium)

Have you tested that this is not an upstream issue or an issue with your configuration?

  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

Several "--enable-features" flags seems to execute only the last one

How to Reproduce?

Add the following lines to a file within /etc/chromium.d/ folder

Option A

export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-features="DisableQRGenerator"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-features=ServiceWorkerAvoidMainThreadForInitialization"

Option B

export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-features=ServiceWorkerAvoidMainThreadForInitialization"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-features="DisableQRGenerator"

Actual behaviour

In both options (A and B) it seems that only the last option becomes effective in the browser.

Expected behaviour

Both of them become effective regardless the order.

Relevant log output

No response

Additional context

No response

@networkException
Copy link
Member

I think --enable-features should simply be used with a comma separated list like this --enable-features=WebUIDarkMode,CopyLinkToText

@carlosfmesilva
Copy link
Author

Hi @networkException, the problem is that the files shipped with ungoogled-chromium have the explained behaviour. Here is a sample of /etc/chromium.d/miscellaneous:

# Disable NGShapeCache
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-features=LayoutNGShapeCache"

# Disable LevelDBProtoAsyncWrite
#export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --disable-features=LevelDBProtoAsyncWrite"

# Enable boosting priority of backend tasks associated with foreground clients for IDB
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-features=IdbExpediteBackendProcessingForForegroundClients"

# Enable ServiceWorkerAvoidMainThreadForInitialization
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-features=ServiceWorkerAvoidMainThreadForInitialization"

Of course we may we may do something like cat * | grep "\-\-enable-features" | grep -v ^# | cut -d= -f3 | sed 's/"//g' | sed -z "s/\n/, /g", and cat * | grep "\-\-disable-features" | grep -v ^# | cut -d= -f3 | sed 's/"//g' | sed -z "s/\n/, /g" to have all the defined preferences for --enable-features or --disable-features in just one line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants