PSA: Removing `--extensions-on-chrome-urls` and `--disable-extensions-except` flags in Chrome branded builds

Hi all,

Starting in Chrome 139, the --extensions-on-chrome-urls and --disable-extensions-except command-line flags will be removed in official Chrome branded builds. This follows the removal of the `--load-extension` flag in Chrome 137.

Please note that this change only applies to Chrome branded builds. --extensions-on-chrome-urls and --disable-extensions-except will continue to function as before in non-Chrome brands, such as Chromium and Chrome For Testing. They will also be available on ChromeOS builds.

This change aims to enhance the security and stability of the Chrome browser for our users. We have observed that both flags are commonly abused to load and obfuscate malicious/unwanted software into the browser.

What this means for your development workflow:

• If you use --extensions-on-chrome-urls for debugging extension pages, you can use a new command-line switch --extensions-on-extension-urls instead in M139. This new switch will be allowed for all extensions.

• For all other use cases of --extensions-on-chrome-urls and --disable-extensions-except, consider using Chromium or Chrome for Testing. The Chrome For Testing build is specifically designed for development and testing and will continue to support both flags

We recognize that this might require changes in your usual process, and we truly appreciate your understanding as we work to improve the security of the Chrome ecosystem and protect our users from potential harm.

If you have any questions or concerns regarding this change, please feel free to reply to this email or reach out through our developer support channels.

Thank you for your understanding and continued dedication to building great extensions for Chrome users.

Thanks,

Richard on behalf of Chrome Counter Abuse