Moving built-in engines to webextensions means we also need a way to define which one is the default search engine. Whatever mechanism does that now just needs to be updated to set the default to the new extension.
This will all be handled by nsSearchService, so this may end up being closed as an unnecessary bug.
Priority: P3 → P2
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1496075
You need to log in before you can comment on or make changes to this bug.