Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

How can a user disable the default search engines already available in FF27?

  • 3 odgovora
  • 14 ima ovaj problem
  • 3 prikaza
  • Posljednji odgovor od Kevin

more options

Recent updates to Firefox mobile disable the user's ability to immediately disable preset search engines (Google, Yahoo, Bing, etc). Current "solutions" that allegedly address this issue involve users having to make changes to json. A user shouldn't have to go beyond the interface(s) readily available through "Customization" option.

I will not be using the current version of your mobile browser because of these anti-features, Mozilla. I would also encourage other users to do the same.

If Mozilla is as committed to Open Source, empowering communities and its users (as its own Manifesto suggests), then Mozilla and Firefox's Devs must necessarily re-examine the flawed thinking that have led to Firefox's recent "nerfing" of user control.

I encourage the Mozilla Foundation, Firefox, and Community Devs to more closely examine the implications of disabling a user's rights to choose for themselves; to disable those features and customizations they choose not to use.

Over the past year, more and more people have stopped trusting the likes of Google, Yahoo, Microsoft, etc. Trust is a very fragile thing indeed. I've trusted Firefox since its early days, but recent changes (like this one) have caused me to question just how much Mozilla wants to empower its users and how much it respects its users' right to control, self-determination, and privacy.

The question now becomes, "Can I trust you?"

Recent updates to Firefox mobile disable the user's ability to immediately disable preset search engines (Google, Yahoo, Bing, etc). Current "solutions" that allegedly address this issue involve users having to make changes to json. A user shouldn't have to go beyond the interface(s) readily available through "Customization" option. I will not be using the current version of your mobile browser because of these anti-features, Mozilla. I would also encourage other users to do the same. If Mozilla is as committed to Open Source, empowering communities and its users (as its own Manifesto suggests), then Mozilla and Firefox's Devs must necessarily re-examine the flawed thinking that have led to Firefox's recent "nerfing" of user control. I encourage the Mozilla Foundation, Firefox, and Community Devs to more closely examine the implications of disabling a user's rights to choose for themselves; to disable those features and customizations they choose not to use. Over the past year, more and more people have stopped trusting the likes of Google, Yahoo, Microsoft, etc. Trust is a very fragile thing indeed. I've trusted Firefox since its early days, but recent changes (like this one) have caused me to question just how much Mozilla wants to empower its users and how much it respects its users' right to control, self-determination, and privacy. The question now becomes, "Can I trust you?"

Svi odgovori (3)

more options

This regressed. There is not a way to disable search engines at this time. This is fixed as of Firefox 29 which will be the code on http://www.mozilla.org/en-US/mobile/aurora/ around Friday this week.

more options

I see that it was "regressed" (this is exactly the reason why I reached out in the first place). Thank you for confirming.

Might inquiring minds ask why this was "regressed"? I think it's important for users to understand the rationale behind such a move, if only to better understand and assess the course the lies ahead for Firefox's presence in the mobile market.

Thanks for the head's up about FF29. I (and I'm sure others) look forward to having this control restored.

more options

We changed from some html/javascript code where the options were in a tab to some Java code where the options are in settings.

Mostly was a timing issue the developers have a lot of requests and will often implement the core features first then add back or fix followup issues with the feature in future versions.