-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Support importing tabs from legacy Brave (Muon) #998
Comments
I'm working on importing pinned sites right now and have run into a design problem that doesn't have an obvious solution. The problem is b-l and b-c handle pinned sites differently: pinned sites are global in b-l, but they are per-window in b-c. Options for how to handle this:
|
How about option 3 - import the pinned tabs ONLY to the FIRST window 😄 |
Fixed with brave/brave-core#981 😄 I renamed this issue (so it reflects that import only happens for Muon Brave) and created a more general issue #2309 |
@garrettr @bsclifton what's the expected result if you had pages like 'about:brave' or 'about:preferences#payments' opened in muon? When those pages are imported to b-c I see the below. (note, about:history seems to have correctly migrated to brave://history) |
@garrettr @bsclifton if I import a muon profile with a bunch of tabs (think 4 windows approx 100 tabs in each window), I beachball for a few seconds and then the fans on my mac start to kick on. it looks like we're loading all tabs simultaneously after import. Subsequent launches of b-c seem to be ok (no fan action) and when I click on a tab that's when it loads. Is this expected? cc @kjozwiak |
Per discussion, some waiting is OK- but the import should be happening async (UI should be responsive, etc) @LaurenWags has logged #2374 to address the issue 😄 👍 |
Verification Passed on
Migrated from muon v0.25.201
Verified passed with
Verification passed on
All import functions on Linux is done via manual import as auto migration is not supported
|
Test plan
See brave/brave-core#981
Description
This would make migration almost completely painless.
The text was updated successfully, but these errors were encountered: