Open Bug 1645183 Opened 1 year ago Updated 11 months ago

DDG default message appears on about:preferences after removing it


(Firefox :: Search, defect, P3)




Tracking Status
firefox78 --- wontfix
firefox79 --- wontfix


(Reporter: pablo.muir, Unassigned)


(Depends on 1 open bug, Blocks 1 open bug)



(1 file)

127.71 KB, image/jpeg
Attached image DDGBug0.jpg

DDG as default message still present even after removig DDG as a search engine in about:preferences#search

Windows 10

Tested with:
Firefox 78.0b5 , Firefox nightly 79.0a1 (june11)

**Steps **
Download latest Romanian Beta firefox build
Install addon
enter about:preferences#search
notice the message "An extension, DuckDuckGo Privacy Essentials, has set your default search engine."
Scroll below, and delete duckduckgo from the list
Duckduck Go has been removed.
Noticed that now GOOGLE is your default, even with the addon still installed.

Actual Results
"An extension, DuckDuckGo Privacy Essentials, has set your default search engine." still shows up, even after restarting.
duckduckgo is not your default anymore and it goes to google default.

Expected Result
its kind of a grey area because the user still has the addon installed and chose to remove duckduckgo from the list of his engines.
Im not sure if google should be default or the DDG with new code should still be default even if user removed it from about:preferences and kept the addon installed.
so its complicated to decide what is the correct result, but differences show because of this.

Group: mozilla-employee-confidential

There's two issues here. The main issue here is that we're not removing the notification when we change the default. Bug 1638888 is probably going to fix that.

Depends on: 1638888
Assignee: nobody → standard8
Severity: -- → S3
Priority: -- → P1

I was wrong about the bugs here, this is actually a result of bug 1546652.

Depends on: 1546652
No longer depends on: 1638888
Assignee: standard8 → nobody
Priority: P1 → P3
Group: mozilla-employee-confidential
You need to log in before you can comment on or make changes to this bug.