Closed
Bug 1437580
Opened 7 years ago
Closed 5 years ago
Search engine name sent to telemetry is inconsistent
Categories
(Firefox :: Search, enhancement, P5)
Firefox
Search
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox60 | --- | affected |
People
(Reporter: mkaply, Unassigned)
Details
We currently send the search engine name to telemetry in four different places and we create the name inconsistently.
https://searchfox.org/mozilla-central/source/browser/base/content/browser.js#3844
is used by
https://searchfox.org/mozilla-central/source/browser/base/content/browser.js#3896
https://searchfox.org/mozilla-central/source/browser/modules/BrowserUsageTelemetry.jsm#108
is used by
https://searchfox.org/mozilla-central/source/browser/modules/BrowserUsageTelemetry.jsm#407
https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/TelemetryEnvironment.jsm#1188
is used by
https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/TelemetryEnvironment.jsm#1230 (marked deprecated in the docs, but we still use it.)
https://searchfox.org/mozilla-central/source/toolkit/components/search/nsSearchService.js#4159
is used by
https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/TelemetryEnvironment.jsm#1231
We should have a consistent API for querying the engine name from the search service (including other- with a completely definition of when to use other)
No one should be generating their own ID.
And we need to figure out why defaultSearchEngine was marked deprecated. We're still using it and it contains different data than defaultSearchEngineData.name (it doesn't contain the other- part).
Comment 1•7 years ago
|
||
This doesn't seem super high priority, so I'll mark it P5, but please feel free to change it.
Priority: -- → P5
Comment 2•5 years ago
|
||
Unfortunately the links are all busted, but I'm pretty sure we're as consistent as we can be now.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•