Add probes for Profile selector dialog / about:profilemanager page
Categories
(Toolkit :: Startup and Profile System, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox137 | --- | fixed |
People
(Reporter: jhirsch, Assigned: jhirsch)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [fidefe-profile-management] )
Attachments
(1 file)
Note that this bug includes either figuring out how to 'forward' telemetry to whatever profile gets chosen, or just firing a ping via pingsender in the background.
Note the probe names are defined here: https://docs.google.com/spreadsheets/d/173QrIOJT4kkyygINoduZhWUG5qf8wnMWfphss0yV8Ug/edit?gid=309210703#gid=309210703
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Mass setting S2 severity for 0.5% release bugs. Apologies for the bug spam!
| Assignee | ||
Comment 2•11 months ago
|
||
Note: when we create the telemetry, we should also instrument the about:preferences "Manage Profiles" button
| Assignee | ||
Updated•11 months ago
|
| Assignee | ||
Comment 3•11 months ago
|
||
Not yet ready to land - for some reason one of the tests is failing with
an error about one of the Glean methods being undefined, yet when I run
the build locally, I see that Glean method.
Also, Glean is not available in early startup, so we need to add a
followup bug to determine if it's worth recording telemetry data in the
case where the window is shown at startup, rather than launched from an
existing Firefox via the 'manage profiles' menu item. I'll file that bug
before landing.
Comment 5•11 months ago
|
||
| bugherder | ||
Description
•