Make WDBA launch Firefox after user accepts return to Firefox prompt
Categories
(Toolkit :: Default Browser Agent, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: nalexander, Assigned: nalexander)
References
Details
Attachments
(4 files)
Right now, when a user accepts the WDBA offer, we use our 1-click set to default code to set Firefox as the default but provide no further feedback. UX review during Bug 1822941 and sibling tickets identified that we could improve this experience by providing some feedback: changing the button to a check mark, or replacing the notification, or launching Firefox at that moment.
It is difficult to understand the effect of the WDBA (and changes to the WDBA) on in-product metrics such as DAU and retention. The simplest way to connect these two things together is for the WDBA to launch Firefox, and either have Firefox set itself as default right then and there, or record that the launch happened due to the WDBA, perhaps with a browser.launched_to_handle
event. That would allow post-hoc analysis to understand how users that return to Firefox via the WDBA behave subsequently.
Assignee | ||
Comment 1•10 months ago
|
||
We would also like to connect users who decline the WDBA offer to in-product metrics, but this ticket (as written) will not achieve that.
Assignee | ||
Comment 2•10 months ago
|
||
This simply makes local testing more pleasant: no need to bump
timestamps and/or toggle the default browser in the registry.
Assignee | ||
Comment 3•10 months ago
|
||
Depends on D179254
Assignee | ||
Comment 4•10 months ago
|
||
Depends on D179255
Assignee | ||
Comment 5•10 months ago
|
||
This uses the existing browser.launched_to_handle :: system_notification
event. This is expedient and looks ahead to
making the WDBA a background task, where we likely will set the
privileged name
of the toast to default-browser-agent
or similar.
The alternative is to add a browser.launched_to_handle :: default_browser_agent
event. I started with this and it's simply
duplication. The data analysis phase will look almost identical with
either implementation: it's either filtering on the event name or on
the name
key in the event extras.
Depends on D179256
Assignee | ||
Comment 6•10 months ago
|
||
N.b. The telemetry event used here already exists and this is a usage congruent with the existing usage. Therefore there's no need for additional data-review.
Pushed by nalexander@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e507a54f620a Pre: Add `--force` argument to Windows Default Browser Agent. r=nrishel https://hg.mozilla.org/integration/autoland/rev/34693c22d4dc Part 1: Prepare to invoke `firefox.exe`. r=nrishel https://hg.mozilla.org/integration/autoland/rev/25924abd314a Part 2: Invoke `firefox.exe -to-handle-default-browser-agent` when returning to Firefox. r=nrishel https://hg.mozilla.org/integration/autoland/rev/5d6127a9b7ed Part 3: Record telemetry event when Firefox is launched from WDBA. r=nrishel
Comment 8•10 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e507a54f620a
https://hg.mozilla.org/mozilla-central/rev/34693c22d4dc
https://hg.mozilla.org/mozilla-central/rev/25924abd314a
https://hg.mozilla.org/mozilla-central/rev/5d6127a9b7ed
Description
•