Default search engine is stuck on DuckDuckGo {FF 86.0]
Categories
(Firefox :: Search, defect)
Tracking
()
People
(Reporter: myron, Unassigned)
Details
Attachments
(1 file)
|
18.62 KB,
image/png
|
Details |
FF86 BC Screenshot 2021-02-18 225358.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
Tried to change the default search engine to Google
Actual results:
Default search engine always default to DuckDuckGo
Expected results:
If Google is set as the default search engine then it should not revert to google.
I can, at least, manually, select the search engine I wish to use. The defect is still there when I start Firefox in Safe Mode.
|
||
Comment 2•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Search' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 3•4 years ago
|
||
Please can you try opening the browser console, and seeing if any errors appear when you try to change the default engine or around that time? Maybe also check just after startup as well.
To open the console go to Tools -> Web Developer -> Browser Console (not the web console).
This is unbelievable. I'm not making it up, but it appears that when I opened the Browser Console, the act of doing so fixed the problem.
I shall try and see if I can trigger the problem and I guess if I can't then this bug report gets closed.
|
|
||
Comment 5•4 years ago
|
||
Did you by any chance have (or still have) DuckDuckGo Privacy Essentials installed at some stage?
Yes, but has been disabled for quite a number of weeks. I enabled it, played with settings, removed the add-on, tried again. Before that I tried with starting FireFox in it's safe mode and the issue was still present there. Right now, as I type this I have the DDG add-on installed, but it's not active. I'll leave it as inactive/disabled and see what happens. It's waiting and observation right now.
I can't trigger the fault right now so I am wondering if it worth closing this bug report as I can't trigger the symptom.
I'm going to put this on the back-burner. I've devoted significant time now to trigger the issue and it's behaving.
Description
•