Closed Bug 1681740 Opened 4 years ago Closed 4 years ago

Extend telemetry for search engine/add-on mismatches to also cover legacy OpenSearch engines

Categories

(Firefox :: Search, task, P2)

task

Tracking

()

RESOLVED WONTFIX

People

(Reporter: standard8, Assigned: standard8)

References

Details

From looking at various data, there are a set of engines in user's profiles where the loadPath looks something like:

jar:[profile]/extensions/<extensionid>.xpi/<filename>.xml

The jar: is optional, and profile may be app instead.

These generally look to be cases where we've not "upgraded" an engine across to the add-on definition. In some of the cases the name of the engine is different, in others, the add-ons have been blocklisted.

As a first step I'd like to add some telemetry that extends or is similar to what we did in bug 1665938. The telemetry should:

  • Identify cases where the add-on is not installed or disabled.
  • Identify cases which could be "upgraded", e.g. the name is different, or it is a case we haven't tried before (e.g. no jar: in the loadPath).

The intent of this telemetry is to check for any likely negative/unexpected effects and help us to validate that "upgrading" an engine would have the expected result.

Blocks: 1446934

Just a note, if we're thinking about allowing the extension id to match, then we should check telemetry to ensure that there's no legacy add-ons with more than one search engine defined.

Having looked at the existing telemetry and thought about it a bit more, I do not think it is worth adding more telemetry for this, we have what we need currently. Therefore I've filed bug 1685748 to make this happen.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.