Closed Bug 1446934 Opened 6 years ago Closed 3 years ago

The Ecosia search engine is reset to Google after migrating to the WebExtension

Categories

(Firefox :: Search, defect, P3)

defect

Tracking

()

RESOLVED FIXED
87 Branch

People

(Reporter: cgeorgiu, Assigned: standard8)

References

Details

(Whiteboard: [fixed by bug 1685748])

[Note]:
- this is a follow-up from bug 1426081 comment 33

[Affected versions]:
- latest Nightly 61.0a1 (2018-03-18)
- Beta 60.0b4 (20180315232954)
- Release 59.0.1 (20180315233128)

[Affected platforms]:
- Windows 10 x64
- macOS 10.13
- Ubuntu 16.04 x64

[Steps to reproduce]:
1. Launch Firefox 56.0.2 on a clean profile.
2. Install version 3.4.5 of the Ecosia add-on from here:  https://addons.mozilla.org/de/firefox/addon/ecosia-the-green-search/versions/?page=1#version-3.4.5
3. Close Firefox. (Ctrl + Shift + Q or Cmd + Q)
4. Open an affected Firefox version (e.g. FF 60.0b4) with the same profile.

[Expected result]:
- The default search engine remains Ecosia.

[Actual result]:
- Ecosia is not remaining the default search engine and is being reset to Google.

[Regression range]:
- I don't think this is a regression, I was able to reproduce it on 58.0.2 and 58.0 as well.
Priority: -- → P3

I've worked out what this is:

In 3.4.5, Ecosia's search engine definition had the name "Ecosia". In 4.x, the style of definition changed with the move to WebExtensions, but they also changed the name to "Ecosia Search".

This defeated the automatic "upgrade" of the search engine to use the WebExtension definition, as that relies on the name matching.

I'm not sure yet if we'll be able to retrospectively fix them, it will need need thinking about - the start of that thinking will be done in bug 1681740.

Depends on: 1681740

This is being fixed by bug 1685748.

Assignee: nobody → standard8
Severity: normal → S3
Depends on: 1685748
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1685748]
Target Milestone: --- → 87 Branch

Older Ecosia add-ons (under 4.x) are no longer accessible so we can't verify this, setting qe-.

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