Skip to content

[Discussion] improve Chromium browser portability #15483

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

Open
BoringBoredom opened this issue May 18, 2025 · 2 comments
Open

[Discussion] improve Chromium browser portability #15483

BoringBoredom opened this issue May 18, 2025 · 2 comments

Comments

@BoringBoredom
Copy link
Contributor

The problem

None of the following popular Chromium browsers are portable in their current manifest forms: Chrome doesn’t support a persistent user directory at all, while Brave and UGC use a custom user directory only in the application shortcut and shim. Opening them by clicking a link in an external application causes them to fall back to the regular user directory.

"shortcuts": [
[
"chrome.exe",
"Chromium",
"--user-data-dir=\"$dir\\User Data\""
]
],

Extras/bucket/brave.json

Lines 30 to 36 in 691fd92

"shortcuts": [
[
"brave.exe",
"Brave",
"--user-data-dir=\"$dir\\User Data\""
]
],

"shortcuts": [
[
"chrome.exe",
"Google Chrome"
]
],

The solution

Add a registry file with the following entry to the scripts folder:

https://chromeenterprise.google/policies/#UserDataDir

Configures the directory that Google Chrome will use for storing user data. If you set this policy, Google Chrome will use the provided directory regardless whether the user has specified the '--user-data-dir' flag or not.

@HUMORCE
Copy link
Member

HUMORCE commented May 18, 2025

In some cases, people just want install alternative browsers instead main browsers via Scoop.

@BoringBoredom
Copy link
Contributor Author

The registry key differs for each browser (for example, Brave). There will be no interference.
In my opinion, Nonportable is the appropriate location for browser manifests that don’t include the policy.

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

No branches or pull requests

2 participants