Closed Bug 1782818 Opened 2 months ago Closed 2 months ago

Add COM Notification Server to MSIX packages.

Categories

(Toolkit :: Notifications and Alerts, enhancement, P2)

Firefox 105
Unspecified
Windows
enhancement

Tracking

()

RESOLVED FIXED
105 Branch
Tracking Status
firefox105 --- fixed

People

(Reporter: nrishel, Assigned: nrishel)

Details

Attachments

(1 file)

Native notifications for MSIX packages should use the COM notification server to handle relaunching Firefox when notifications are interacted with after Firefox has closed.

Now that https://phabricator.services.mozilla.com/rMOZILLACENTRAL1bf6f44257d83deafd5ca47cb3067f95e26fae27 has landed, MSIX notifications display correctly, but firefox.exe is launched with the appended notification arguments instead of notificationserver.dll. This results in a new window opening with nonsensical tabs related to the launch arguments. Using the notification server should fix this.

Type: task → enhancement

This converges Windows native notification behavior across all installers to use the COM notification server.

This also fixes an issue where interacting with an MSIX notification opened a new window with new tabs correlated to the toast notification launch arguments. MSIX by default calls the application sending a notification with the provided launch arugments, which was an problem as we use launch arguments in the COM server to reconstruct the origin of a notification.

Pushed by nrishel@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/db65aa1a08a0
Use COM notification server for toast notifications in MSIX packages. r=nalexander,Jamie
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
You need to log in before you can comment on or make changes to this bug.