Adapt the data import wizard to use the original $HOME on Linux

We change $HOME on Linux for various reasons, but this prevents the import procedure from working, plus maybe other disadvantages.

While exploring this might require more time (we have mullvad-browser#170 for it), we can probably adjust the paths Firefox uses for importing the data to use a (different) environment variable.

marked this issue as related to mullvad-browser#170

added 13.5 stable Doing Linux Sponsor 131 labels

assigned to @pierov

mentioned in issue mullvad-browser#170

The migration wizard is implemented on its own in browser/components/migration/content/migration-dialog-window.html and browser/components/migration/content/migration-wizard.mjs.

browser/components/migration/content/migration-wizard-constants.mjs has some interesting constants we could use to find where the checkbox to import stuff are created. In particular, the resources Firefox can look for are:

• history
• form data
• passwords
• bookmarks
• payment methods

I think at the moment we want only bookmarks.

The actual migration happens elsewhere, and the communication is done through custom events. In particular, we're looking for "MigrationWizard:BeginMigration".

Migrators are implemented in a very OOP-fashion. For example, one file is browser/components/migration/ChromeProfileMigrator.sys.mjs. Notice the browser/components/migration directory.

I think we're interested especially in the Chromium-based browser and maybe on Firefox.

So, I'm starting to dig them.

Found it!

Probably we can do something like

        let targetPath =
          rootDir === "Home" && Services.env.get("BB_ORIGINAL_HOME")
            ? Services.env.get("BB_ORIGINAL_HOME")
            : Services.dirsvc.get(rootDir, Ci.nsIFile).path;

For Firefox it's much more complicated, and I believe it doesn't work on the other platforms as well, because it tries to look for profiles.

Maybe you can import from the other MB profiles .

For Firefox it's much more complicated

Yep. It tries to do smart thing, and re-use the profiles that were found during the startup.

I thought about extending nsIToolkitProfileService to list another directory, but the fact is that the list is modified by its contents.

Maybe at the end of the day writing a new simplified module for handling Firefox would work better, especially since we're interested only in bookmarks at the moment.

mentioned in merge request !931 (merged)

marked this issue as related to tor-browser-build#41094 (closed)

marked this issue as related to tor-browser-build#41095 (closed)

mentioned in merge request tor-browser-build!931 (merged)

added Needs Review label and removed Doing label

Just tested on Windows as well, it shows favorites instead of bookmarks for Internet Explorer as expected.

closed