Open Bug 621957 Opened 14 years ago Updated 14 years ago

Profile migration (per -migration) imports into current profile

Categories

(SeaMonkey :: Startup & Profiles, defect)

Product:
SeaMonkey
Component:
Startup & Profiles
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: mnyromyr, Unassigned)

Details

If you start SM with -migration, the migration wizard try to import the selected profile into the currently running profile. This is not a problem if you start SM2 for the first time or use -profile to specify an empty location, but it's extremely surprising (and usually not what you want) if you already have other profiles - personally, I expected the profile wizard to create a new profile named like the imported one (if possible). (Depending upon the target profile, migration might also just crash, because the migrated data is not compatible with existing stuff - I experienced that twice before realizing that it tried to import stuff in my last-used profile!) The migration wizard should ask which profile to import into if there is a choice or at least tell which target profile it will use.
That's intended behavior, I suggest WONTFIX.
Confusion and surprising behaviour are intended behavior?!
Not confusion and surprise, but importing into the current profile is. Just means that this may need better docs, feel free to write them up.
You need to log in before you can comment on or make changes to this bug.