Closed Bug 1643858 Opened 4 years ago Closed 4 years ago

Search engine is not restored/reset when the add-on is uninstalled at early startup

Categories

(WebExtensions :: General, defect, P3)

defect
Points:
5

Tracking

(firefox84 verified)

VERIFIED FIXED
84 Branch
Iteration:
84.2 - Nov 2 - Nov 15
Tracking Status
firefox84 --- verified

People

(Reporter: robwu, Assigned: standard8)

References

Details

Attachments

(1 file)

STR:

  1. Install a search engine, e.g. https://addons.mozilla.org/en-US/firefox/addon/bing-search-engine-/versions/
  2. In the "[name] would like to change your default search engine ..." prompt, choose Yes.
  3. Quit Firefox.
  4. Delete the extension file - extensions/{8d8ca802-6b23-43ed-9445-e05d48579542}.xpi
  5. Start Firefox and check your default search engine

Expected:

  • It should be the default search engine from a fresh install, e.g. Google.

Actual:

  • The engine that you had installed in step 1, i.e. Bing Search.

Hey Mark, can you please look into this?

Flags: needinfo?(standard8)

I came across this the other day that looks suspicious:

https://searchfox.org/mozilla-central/rev/0e09b9191c02097034e46b193930f91c45b7885d/browser/components/extensions/parent/ext-chrome-settings-overrides.js#240

We don't seem to be handling that here, which is where I'd expect:

https://searchfox.org/mozilla-central/rev/0e09b9191c02097034e46b193930f91c45b7885d/toolkit/components/search/SearchService.jsm#1717

So assuming the removeEngine in the WebExtension part is being called, then we probably need to handle this correctly in the search service.

I need to look at this a bit more, and it might be related to a bug we've just discussed with QA, so I'll leave the NI open and hopefully have a look at it in more detail next week.

I've started to look at this, I don't think it is too urgent, but would be good to get fixed anyway whilst we're doing search service cleanup.

Assignee: nobody → standard8
Status: NEW → ASSIGNED
Flags: needinfo?(standard8)

The severity field is not set for this bug.
:mixedpuppy, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mixedpuppy)
Severity: -- → S3
Flags: needinfo?(mixedpuppy)
Priority: -- → P3
Iteration: --- → 83.1 - Sept 21 - Oct 4
Points: --- → 5
Iteration: 83.1 - Sept 21 - Oct 4 → 84.1 - Oct 19 - Nov 01
Iteration: 84.1 - Oct 19 - Nov 01 → 84.2 - Nov 2 - Nov 15
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d18224bb657a
When an add-on is uninstalled at early startup, ensure that we also remove associated search engines. r=mixedpuppy,daleharvey
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
Flags: qe-verify+
See Also: → 1675506

I have managed to reproduce the issue using Fx79.0a1.
The issue is verified fixed using the latest Fx84.0a1 on Windows 10, Ubuntu 18.04 and macOS 10.14. The switch back to the default engine is done successfully after the addon removal.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: