Bugzilla

@Kagami It seems that the correct way to handle this is to check the notification history for an active toast in the case of dismissal (we could count the dismissals but as shown above we may not receive more than one). That said I'm not yet certain how changes necessary for notifications that persist and are interactive after Firefox is closed will impact how we track handlers.

Also it seems that there's a platform encouraged way to add [dismiss all](https://docs.microsoft.com/en-us/windows/apps/design/shell/tiles-and-notifications/toast-schema#toastbuttondismiss) to a toast message, therefore the toast's x button should be treated as hide instead of dismiss all.

@Kagami It seems that the correct way to handle `mActiveHandlers` growth this is to check the notification history for an active toast in the case of dismissal (we could count the dismissals but as shown above we may not receive more than one). That said I'm not yet certain how changes necessary for notifications that persist and are interactive after Firefox is closed will impact how we track handlers.

Also it seems that there's a platform encouraged way to add [dismiss toast and action center notifications](https://docs.microsoft.com/en-us/windows/apps/design/shell/tiles-and-notifications/toast-schema#toastbuttondismiss), therefore the toast's x button should be treated as hide instead of dismiss all.