Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How to change the search provider when using the Firefox Home Button Search feature?

  • 2 پاسخ
  • 5 have this problem
  • 3 views
  • آخرین پاسخ توسّط mrt181

more options

In Firefox itself I have configured duckduckgo as my default search provider.

But when I use the Firefox Home Button Search it is always set to google and I do not see any option to change that?

I like the Firefox Home Button Search (or whatever it's called) otherwise, but it's annoying that it does not use the default from Firefox.

I use the Google Now Launcher.

In Firefox itself I have configured duckduckgo as my default search provider. But when I use the Firefox Home Button Search it is always set to google and I do not see any option to change that? I like the Firefox Home Button Search (or whatever it's called) otherwise, but it's annoying that it does not use the default from Firefox. I use the Google Now Launcher.
Attached screenshots

Modified by mrt181

Chosen solution

hi mrt181, it is intended to use the same search engine as in firefox - however there's a bug at the moment, so it doesn't apply in all situations. usually it will be enough to switch the default engine in firefox back and forth once to work around the issue in the search widget and get the same search provider as set in the browser.

Read this answer in context 👍 4

All Replies (2)

more options

Chosen Solution

hi mrt181, it is intended to use the same search engine as in firefox - however there's a bug at the moment, so it doesn't apply in all situations. usually it will be enough to switch the default engine in firefox back and forth once to work around the issue in the search widget and get the same search provider as set in the browser.

more options

philipp said

...usually it will be enough to switch the default engine in firefox back and forth once to work around the issue...

Thank you, problem resolved