Deleting the last but one profile doesn't remove the profile avatar from the other running profile
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
People
(Reporter: mossop, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-profile-management])
If you have two profiles in total and both of them open they both display the avatar in the dock. If you then delete one of the profiles you are left with a single profile running and it still displays the avatar when it should be removed at that point.
Profiles need to signal existing instances when they are being deleted to allow them to update their dock icon if needed.
Reporter | ||
Updated•23 days ago
|
Updated•23 days ago
|
Comment 1•14 days ago
|
||
From KimB: we actually want to keep the avatar in the dock at this point, for cases where users are deleting then recreating profiles in a group. Is there any work needed to make sure we consistently show the avatar in such a case?
Reporter | ||
Comment 2•14 days ago
|
||
(In reply to Jared Hirsch [:jhirsch] (he/him) (Needinfo please) from comment #1)
From KimB: we actually want to keep the avatar in the dock at this point, for cases where users are deleting then recreating profiles in a group. Is there any work needed to make sure we consistently show the avatar in such a case?
Depends what exactly we want to do. If we just want to leave the badge on the dock icon until the user restarts the sole remaining profile then there is nothing to do and we can close this.
If we want to remove the badge immediately but then re-add it when the user creates a new profile then we have to do the work described in comment 0.
If we want to remove the badge after a time if the user hasn't created a new profile then we want to do the work in comment 0 and include some timeout in it.
I'm inclined to leave the badge until restart (and not just because we don't have to do anything) -- mainly because we'd be guessing about what the timeout should be. We can always revisit this later and/or watch for user feedback -- and I'm also curious about whether persisting the badge until restart might tempt the user to go back in and give Profiles a try again.
Comment 5•14 days ago
•
|
||
Pinged UX on slack and misha agreed with kim's take in comment 4: for now, it's good enough to leave the remaining profile's firefox logo badged for the rest of the current browsing session, then not show it on restart if they haven't created additional profiles.
I think this means we can safely ignore this bug for the 0.5% release. Moving to the future metabug, in case we want to revisit later.
Description
•