1862016 - Resolve race between Windows native notification actions and Firefox startup actions like the check default browser prompt

Status: NEW

(Toolkit :: Alerts Service, defect, P3)

Description

[Nick Alexander :nalexander [he/him]]

Bug 1805514 added the capability for Windows native notifications to invoke arbitrary Special Message Actions when relaunching Firefox. The first use case was to be "Set Firefox as Default"... but it turns out that acting on the Special Message Action (here) races with Firefox startup actions such as the check default browser prompt (here).

This ticket tracks resolving this race, perhaps by understanding why various tab opening SMAs required the tick-delay currently in the code.

Comment 1

[Nick Alexander :nalexander [he/him]]

(In reply to Nick Alexander :nalexander [he/him] from comment #0)

Bug 1805514 added the capability for Windows native notifications to invoke arbitrary Special Message Actions when relaunching Firefox. The first use case was to be "Set Firefox as Default"... but it turns out that acting on the Special Message Action (here) races with Firefox startup actions such as the check default browser prompt (here).

To be clear: the SMA that sets Firefox as default is processed, it just happens after the prompt is displayed, yielding an awkward user experience.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1805514

Comment 3

[:Gijs (he/him)]

If the SMAs are reasonably quick to execute (not, like, "ping a server and wait for a response and then do X"), perhaps we can "just" make the BrowserGlue stuff await the processing of the SMAs?

Comment 4

[Dianna Smith [:diannaS]]

:nick is this something you are planning to address for fx120? also can you set priority/severity on this as well?

Comment 5

[Nick Alexander :nalexander [he/him]]

(In reply to Dianna Smith [:diannaS] from comment #4)

:nick is this something you are planning to address for fx120? also can you set priority/severity on this as well?

No, not tracking 120. I've set P1 (Mozilla should do this) and SN/A ('cuz it has no impact unless we mistakenly exercise this particular case).

Comment 6

[Ryan VanderMeulen [:RyanVM]]

Based on comment 5, setting to P3/S4 as a backlog bug with low severity.