Bug 1666651 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

There are two possible bugs being reported here:
         First is the dupe after bug 1538668, which causes @google to be added as a pinned search tile when the default search engine is switched from google to ddg.
         Second would be that the ddg gets defaulted to google. 

For the first issue, when you switch from google to ddg, automatically an @google pinned search shortcut is added to the topsites, I'm guessing this might be intended and tracked in bug 1538668.

For the second issue, that is a bit more interesting, I've tried to reproduce the update path from 81.0b9 devedition to 82.0b2 devediton (windows10 and mac 10.13.6) and I didn't get my default engine switched from ddg to google.

@Albert, could you please list here if you are using a localized build and on which region you are currently set (about:config and list the value for browser.search.region).

@Mark might have an idea how to get a postfact glimpse of what happened with your upgrade that caused default search engine to be switched from ddg to google.
There are two possible bugs being reported here:
         
* First is the dupe after bug 1538668, which causes @google to be added as a pinned search tile when the default search engine is switched from google to ddg.
* Second would be that on upgrade path the ddg gets defaulted to google. 

For the first issue, when you switch from google to ddg, automatically an @google pinned search shortcut is added to the topsites, I'm guessing this might be intended and tracked in bug 1538668.

For the second issue, that is a bit more interesting, I've tried to reproduce the update path from 81.0b9 devedition to 82.0b2 devediton (windows10 and mac 10.13.6) and I didn't get my default engine switched from ddg to google.

@Albert, could you please list here if you are using a localized build and on which region you are currently set (about:config and list the value for browser.search.region).

@Mark might have an idea how to get a postfact glimpse of what happened with your upgrade that caused default search engine to be switched from ddg to google.

Back to Bug 1666651 Comment 1