1879069 - The WDBA toast notification is no longer triggered

Status: RESOLVED WORKSFORME

(Toolkit :: Default Browser Agent, defect)

Description

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Attachment: no WDBA toast notification.mp4

[Notes]:

• We cannot verify if this issue is also reproducible on Firefox Beta 123.0b7 and the latest Nightly 124.0a1 due to the fact that the "Firefox Default Browser Agent" task is not available on these versions, see Bug 1879067.
• We have also verified on Firefox Release 120 and 121, and the WDBA notification is not triggered.

[Affected versions]:

• Firefox Release 122.0.1 (Build ID: 20240205133611)

[Affected Platforms]:

• Windows 10
• Windows 11

[Prerequisites]:

• Have a new Firefox installed.

[Steps to reproduce]:

1. Set Firefox as the default browser.
2. Close the Firefox browser.
3. Open the Edge browser and set it as default.
4. Change the System Date 1 day in the feature.
5. Observe the behavior.

[Expected result]:

• The WDBA toast notification is triggered and displayed.

[Actual result]:

• The WDBA toast notification is NOT triggered.

[Additional Notes]:

• In order to reproduce this issue I have used Windows Sandbox to have a clean environment.
• Attached is a screen recording of the issue.

Comment 1

[Nick Rishel [:nrishel]]

Is this reproducible with [path to firefox] --backgroundtask defaultagent do-task asdf --force? If not this likely has the same root cause as 1879067.

I believe D201034 should fix this, but we should verify with a branded build.

Comment 2

[Nick Rishel [:nrishel]]

Just confirmed this fixed with Bug 1879067 in current Nightly; leaving issue open for QA to follow up.

Comment 3

[Cosmin Muntean [:cmuntean], Ecosystem QA]

After more investigations, we found out that the steps described in comment 0, don't trigger the WDBA notification even on the latest Nightly 124.0ai build with the patch from Bug 1879067.

However, we managed to trigger the notification with the following steps:

1. Set Firefox as the default browser.
2. Close the Firefox browser.
3. From the Windows "Task Scheduler" app -> extend "Task Scheduler Library" "Mozilla" and run the "Firefox Default Browser Agent" task.
4. Open the Edge browser and set it as default.
5. From the Windows "Task Scheduler" app -> extend "Task Scheduler Library" "Mozilla" and run again the "Firefox Default Browser Agent" task.
6. Observe the behavior.

Results: The notification is triggered.
The main difference with the Steps from comment 0 is that now we run the "Firefox Default Browser Agent" task after we set Firefox as the default browser.

In the past when we verified the WDBA notification, we managed to trigger it with the steps mentioned in comment 0. But probably we tested on machines where the "Firefox Default Browser Agent" task was already run when Firefox was set as default.
We will also update our test cases with the new steps in order to trigger the notification.

Considering the above, I will mark this issue as Resolved - WORKSFORME.