Search engine is not restored/reset when the add-on is uninstalled at early startup
Categories
(WebExtensions :: General, defect, P3)
Tracking
(firefox84 verified)
Tracking | Status | |
---|---|---|
firefox84 | --- | verified |
People
(Reporter: robwu, Assigned: standard8)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
STR:
- Install a search engine, e.g. https://addons.mozilla.org/en-US/firefox/addon/bing-search-engine-/versions/
- In the "[name] would like to change your default search engine ..." prompt, choose Yes.
- Quit Firefox.
- Delete the extension file -
extensions/{8d8ca802-6b23-43ed-9445-e05d48579542}.xpi
- 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.
Assignee | ||
Comment 2•4 years ago
|
||
I came across this the other day that looks suspicious:
We don't seem to be handling that here, which is where I'd expect:
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.
Assignee | ||
Comment 3•4 years ago
|
||
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.
Comment 4•4 years ago
|
||
The severity field is not set for this bug.
:mixedpuppy, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Comment 7•4 years ago
|
||
bugherder |
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 8•4 years ago
|
||
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.
Description
•