Log engagement event regardless of recording being enabled
Categories
(Firefox :: Address Bar, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox109 | --- | unaffected |
| firefox110 | --- | verified |
People
(Reporter: mak, Assigned: mak)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
For debugging purposes it seems useful to log the engagement telemetry regardless of it being reported upstream.
|
Assignee | |
Comment 1•2 years ago
|
||
Logs engagement telemetry for debug purposes, regardless of it being reported
upstream.
Also changes a couple other logs to make browser.urlbar.logLevel = "Info"
more readable and usable.
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
|
||
Comment 4•2 years ago
|
||
The glean engagement telemetry is now (Firefox110+) listed in browser console while the browser.urlbar.logLevel is set to Info level, regardless of the value of browser.urlbar.searchEngagementTelemetry.enabled. This raised the question of QA verifying that the glean telemetry is not actually recorded when browser.urlbar.searchEngagementTelemetry.enabled is set to false or when the browser.urlbar.searchEngagementTelemetry.enabled set true, but global telemetry is disabled. FYI, I've asked :daisuke how to acomplish the above offline.
Description
•