avoid changing process AUMID during MSIX taskbar pinning
Categories
(Firefox :: Shell Integration, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: ericchen647, Assigned: ericchen647)
References
Details
(Whiteboard: [fidedi-ope])
Attachments
(1 file)
Currently PinCurrentAppToTaskbarWin11
swaps the Firefox process AUMID to the shortcut's AUMID before calling the pinning API, this is necessary for pinning to work on Win32. After pinning is complete, we switch the process AUMID back to the original one using GenerateAppUserModelID
. This function will always provide the correct original AUMID for Win32 Firefox builds.
However, MSIX Firefox also goes through this code path, even though it's pinning mechanism have major differences from Win32, listed here:
- We can pin MSIX Firefox without doing the AUMID swaps, since the application is already packaged & recognized by the OS
- A MSIX app registers its AUMID with Windows at install time, and its process is expected to always have that AUMID. We shouldn't change it
- The way that
GenerateAppUserModelID
is written means it will never return the correct value for MSIX Firefox builds, by chance this code works for MSIX even though it calls the function
The easiest fix for all of this is to add if conditions that prevent the AUMID-setting code to run if we're in MSIX. This means the process AUMID will never change yet pinning should still work
Updated•6 months ago
|
Updated•6 months ago
|
Comment 3•5 months ago
|
||
Backed out for causing bc failures at browser_processAUMID.js
Comment 5•5 months ago
|
||
bugherder |
Description
•