-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Upgrade to the next generation of Brave browser (brave-core) #4
Comments
@caspertone2003 I maybe have a clean solution with a patch of Chromium. I will open a PR on brave-core repository when my tests are ok. |
Don't know if it is of any help, but Iridium Browser has an official portable version and it's also Chromium based. They recommend creating a shortcut using |
@bnscv |
This comment has been minimized.
This comment has been minimized.
@caspertone2003 Post a message here if you want to know : brave/brave-core#795 |
@caspertone2003 Nop it's not. I only wait until my PR is approved before resolving conflicts. No need to work for nothing 🙃 |
Some caveats to note before an upgrade to the next generation of Brave browser.
Passwords are not saved
Brave (as Chromium) stores passwords in such a way that they are encrypted in a way tied to current PC. While the passwords are not kept or left behind on the PC itself, they won't be retrievable when you move to a new PC.
Certificates not portable
Brave (as Chromium) has no certificate manager. It uses Windows certificates manager. So, any certificates you install through the Brave interface are stored on the current local machine and will not be portable.
Some settings and extensions are locked per machine
Brave (as Chromium) locks specific settings to a given PC. This behavior is by design by the Chromium team. If you would like this changed, please open an issue on the brave-core repository. A suggested workaround is to sign in to Brave Safe Storage to restore all settings and extensions but this is not available on the current release of Brave.
And as stipulated in this thread :
These issues are specific to Brave due to Chromium's design and not something we can work around without fixes to brave-core.
Import profile data from Muon
The current stable release (0.55) cannot handle migration of profile data from Muon but there is a work in progress. See brave/brave-core#729
Linked threads
The text was updated successfully, but these errors were encountered: