Closed
Bug 1998148
Opened 11 months ago
Closed 11 months ago
Pinned Profile shortcut behaves as a Generic Nightly and unpins incorrectly
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1948912
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox144 | --- | unaffected |
| firefox145 | --- | unaffected |
| firefox146 | --- | affected |
People
(Reporter: sbadau, Unassigned)
References
Details
Attachments
(1 file)
|
4.89 MB,
video/mp4
|
Details |
Found in
- Nightly 146.0a1
Affected versions
- Nightly 146.0a1
Tested platforms
- Affected platforms: Windows 11 x64
Preconditions
- Ensure at least one switchable profile exists - Profile A.
- A shortcut for Profile A is created via about:editprofile.
- A Nightly shortcut (that is not linked to any specific profile) is created.
- Ensure no Nightly icon is pinned to the Taskbar.
Steps to reproduce
- Launch Profile A.
- In the Taskbar - right click on Profile A, "Show more actions" and and select "Pin to Taskbar".
- In the Taskbar - click on the Nightly icon that was just pinned.
- Right click on the Firefox Nightly desktop shortcut, click on "Show more options" and select "Unpin from Taskbar".
Expected result
- In all the bellow steps - Nightly should behave in the same way as when Profile A is pinned from the context menu (right Click on Profile A icon -> Show more options and click Pin to Taskbar)
- In step 2 - Profile A should be pinned to the Taskbar.
- In step 3, Profile A should open.
- In step 4 - "Unpin from Taskbar" option should not be displayed for the generic Firefox Nightly shortcut, since Profile A was pinned.
Actual result
- In step 2 - Profile A is not truly pinned to the Taskbar.
- In step 3 - the Profile Selector opens instead of directly launching Profile A.
- In step 4 - the Nightly icon that was pinned from Profile A becomes unpinned from another Nightly desktop shortcut (from the generic one.)
Regression range
- not a regression.
| Reporter | ||
Updated•11 months ago
|
status-firefox144:
--- → unaffected
status-firefox145:
--- → unaffected
status-firefox-esr115:
--- → unaffected
status-firefox-esr140:
--- → unaffected
You need to log in
before you can comment on or make changes to this bug.
Description
•