Closed
Bug 1894526
Opened 6 months ago
Closed 2 months ago
Migrate addons-search-detection away from browser.telemety event APIs
Categories
(Toolkit :: Telemetry, task, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
131 Branch
Tracking | Status | |
---|---|---|
firefox131 | --- | fixed |
People
(Reporter: chutten, Assigned: chutten)
References
Details
Attachments
(1 file)
As the only active system addon that uses browser.telemetry.*
event registration and recording APIs, addons-search-detection will need to be migrated away from using those APIs.
This bug is about:
- Defining addons-search-detection's events in-tree in Events.yaml, instead of via
browser.telemetry.registerEvents
- Defining Glean events that will mirror to those events
- Recording data using Glean APIs (which will then mirror the data to Legacy Telemetry) instead of via
browser.telemetry.recordEvent
Updated•6 months ago
|
Assignee: nobody → tlong
Priority: -- → P1
Comment 1•3 months ago
|
||
Comment 2•3 months ago
|
||
Untaking this after discussing it with chutten. WIP patch attached to this bug.
Assignee: tlong → nobody
Priority: P1 → P2
Assignee | ||
Updated•3 months ago
|
Assignee: nobody → chutten
Severity: -- → N/A
Status: NEW → RESOLVED
Closed: 3 months ago
Priority: P2 → P1
Resolution: --- → FIXED
Assignee | ||
Updated•3 months ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•3 months ago
|
Attachment #9416652 -
Attachment description: WIP: Bug 1894526 - Migrate addons-search-detection away from browser.telemety event APIs. → Bug 1894526 - Migrate addons-search-detection away from browser.telemety event APIs. r?TravisLong!,robwu!
Pushed by chutten@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/85c2532f56b5
Migrate addons-search-detection away from browser.telemety event APIs. r=TravisLong,extension-reviewers,robwu
Comment 4•2 months ago
|
||
bugherder |
Status: REOPENED → RESOLVED
Closed: 3 months ago → 2 months ago
status-firefox131:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•