Closed Bug 1235332 Opened 9 years ago Closed 9 years ago

about:profiles does not remember last used profile when start -P option

Categories

(Toolkit :: Startup and Profile System, defect)

46 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1239848
Tracking Status
firefox46 + fixed

People

(Reporter: alice0775, Unassigned)

References

Details

(Keywords: regression)

[Tracking Requested - why for this release]: STR 0. Provide many profile 1. start firefox.exe -P 2. Select a profile and Start Nightly and then exit 3. start firefox.exe -P Actual Results: about:profiles does not remember last used profile Expected Result: about:profiles should remember last used profile
This combined with the fact that the list is very long and not keyboard navigable and all the items in it are really large means that I now waste >5s every time I have to start a regular nightly off my desktop and pick a profile (usually the same, non-default, one). My workflow used to work like this: 1. turn on machine in the morning 2. open default browser (fx beta) with "default" profile 3. do work, which repeatedly involved: 4: ./mach run -P <whatever> and 5: doubleclick desktop item which points to nightly with -no-remote and -P. It used to be that the first time I ran (5), I would hit down arrow twice, hit enter, and it'd work. And every time after that, I could just hit enter. Now I have to scroll through the list, find the right profile, click the start button. Every time. I realize that there are several changes involved here (the UI, the keeping of the default, the lack of keyboard nav). It seems a lot of it could be avoided if the version of the page that loads for the -P switch hides all the management UI by default using CSS, and adds a separate button to go into "edit" mode. Then the list can be much much smaller, listing only profile names and radio buttons for each profile. And yes, it should remember the last used profile, as this bug says... Andrea, are you still working on this?
Flags: needinfo?(amarchesini)
Tracking since this is a very noticeable user-facing issue. I think this will be addressed in bug 1232629.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.