1942198 - Add telemetry to profiles beforeunload prompt

Status: RESOLVED FIXED

(Toolkit :: Startup and Profile System, task, P1)

Description

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Split out from bug 1941698 as getting the beforeunload prompt telemetry working is proving somewhat complex

Comment 1

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Attachment: Bug 1942198 - Add Glean and legacy telemetry to profiles beforeunload prompt. r?#profiles-reviewers

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/7cafecc72a35
Add Glean and legacy telemetry to profiles beforeunload prompt. r=profiles-reviewers,mossop

Comment 3

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/7cafecc72a35

Comment 4

[Simona Badau, Desktop QA, PTO 22-30June]

Jared, could you please confirm if the parameters and scenarios I used in about:glean are correct for verifying this bug? Please let me know if additional verifications are required for the patch from this report.

Here are the steps that I used:

1. Launched Nightly with a new profile.
2. Clicked on Profiles -> New profile.
3. Profile A is opened.
4. In profile A in a new tab: I navigate to about:glean, assigned a unique tag to the pings (1), set pings to events (2) and clicked on "Apply settings and submit ping" (4).
5. In profile A: I go back to about:newprofile and attempted to close the tab without saving a profile name.
6. The "Leaving without naming this profile" dialog with "Cancel" and "Leave" buttons is displayed.
7. Clicked any of the "Cancel" and "Leave" buttons.
8. In the about:glean tab, clicked again on "Apply settings and submit ping" (4).
9. Checked the Glean Debug Ping Viewer for events under the tag assigned in step 4.
   ---> under the details of the Event I see the following:
   --profiles.new.alert 11921 {"value": "cancel", "glean_timestamp": "1737996119227"} - if I click the "Cance"l button in step 7.
   -- profiles.new.alert 0 {"value": "leave", "glean_timestamp": "1737996163817"} - if I click the "Leave" button in step 7.

I repeated the above steps but navigated to about:editprofile in step 5. Observed the following events:
-- profiles.existing.alert 0 {"value": "leave", "glean_timestamp": "1737995945822"}
-- profiles.existing.alert 56104 {"value": "cancel", "glean_timestamp": "1737995868823"}