Unpin from taskbar option does not appear in the context menu of the Private icon from the installation folder after the Private browsing was previously pinned to taskbar
Categories
(Firefox :: Installer, defect, P3)
Tracking
()
People
(Reporter: gmoldovan, Unassigned)
References
Details
Attachments
(1 file)
|
1.30 MB,
image/gif
|
Details |
Pintotaskbar.gif
Found in
- 106.0b4
Affected versions
- 107.0a1
- 106.0b
Tested platforms
- Affected platforms: Win 10, Win 11
- Unaffected platforms: Win 7
Steps to reproduce
- Launch Firefox.
- Open a New Private Window from the App Menu.
- Pin Private browsing to taskbar.
- Go to the installation folder.
- Right click on the private browsing icon.
- Observe the context menu.
Expected result
- Context Menu should not have Pin to taskbar option, but Unpin to taskbar.
Actual result
- Context Menu has Pin to taskbar option.
Regression range
- We will find the regression asap, if there is one.
Additional notes
- Screencast attached to observe the issue.
- x32.msi builds are not affected, the Unpin from taskbar option is available in the context menu of the installation folder
- If the option Pin to taskbar is clicked again the Private browsing icon changes to a blank icon.
- Reproducible with normal Firefox icons as well.
|
Reporter | |
Updated•2 years ago
|
|
||
Comment 1•2 years ago
|
||
It seems like this is a Windows bug, although we may be able to influence it in some way. I can reproduce this issue whenever I have a shortcut with an AUMID set. It happens with both Firefox shortcuts that the installer creates, the pre-existing Microsoft Edge shortcut -- and even with a shortcut to regedit.exe if I have an AUMID set on it.
My guess is that Explorer doesn't recognize that the app is already pinned because the exe itself has no AUMID associated with it. It's not totally clear to me why it replaces the existing one instead of pinning a second app -- but perhaps it uses the "Description" for that part rather than AUMID?
I'm not sure exactly what we can do about this. Creating a shortcut without an AUMID set would be the obvious thing to do -- but this will mess up taskbar grouping. Clicking that icon on the taskbar will launch Firefox, but it will group under a separate instance of the same icon (grouping is done by AUMID, which we set early in startup).
The best idea I can come up with is to inspect our launch shortcut and fix the AUMID on it.
In any case, I think this is a quite low priority bug given that most people will be using shortcuts that either our installer or Firefox itself will create.
Description
•