-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Import Extensions from Chrome using importer and brave://welcome onboarding #7974
Comments
I think chromium's extension sync logic could be helpful because chrome is syncing extension list and it installs synced list in background. After getting extensions list from chrome's user dir, install logic could be reused. Or it can give some clues to this task done easily. |
BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. NOTE: this commits has many cleanup changes around importing area that uses deprecated patching style. fix brave/brave-browser#7974
BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. NOTE: this commits has many cleanup changes around importing area that uses deprecated patching style. fix brave/brave-browser#7974
BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. NOTE: this commits has many cleanup changes around importing area that uses deprecated patching style. fix brave/brave-browser#7974
BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. NOTE: this commits has many cleanup changes around importing area that uses deprecated patching style. fix brave/brave-browser#7974
BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. NOTE: this commits has many cleanup changes around importing area that uses deprecated patching style. fix brave/brave-browser#7974
BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. BraveExternalProcessImporterHost will fetch available extensions list and ask to install them. Other importing options are done via other utility process but importing extension should be done in browser process. So, BraveExternalProcessImporterHost manages extension installs. NOTE: this commits has many cleanup changes around importing area that uses deprecated patching style. fix brave/brave-browser#7974
Verified passed on macOS Mojave 10.14.6 with
Tested using: Honey, Grammarly Note - state is not persisted (must re-log in to all extensions), confirmed with @bsclifton. This will be covered by a separate issue #8847. Verified passed on macOS High Sierra 10.13.6 with
Verification PASSED on
Verification passed on
Tested using: Honey, Grammarly, Lastpass, Pocket, google translate Verification passed on
|
Description
Users are able to import from Chrome, Firefox, Edge, Safari (options can depend on their platform).
They can import bookmarks, passwords, etc. But there is currently no way to import extensions and extension settings
Offering this would be a great way to make Brave easier to switch to
Steps to Reproduce
Actual result:
No way to import extensions☹️
Expected result:
You should be able to import extensions
The text was updated successfully, but these errors were encountered: