460623 - Google searches for Firefox could be faster

Status: RESOLVED DUPLICATE of bug 511017

(Firefox :: Search, defect)

Description

[Kabection]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1

	
I tried not yet in other languages (English, Spanish, etc ...) but
I discovered that when a person is searching on Google for bar
located on the right from above, the script makes the search with the
following algorithm: (http://www.google.com/search?q=pesquisa) where
research is the subject of research. To improve the polls, not
would be smart to search and are thus: (http://www.google.com.br/
search? q = search)? It seems stupid but by my tests it
make the searches on Google at least a little faster as
IE does. I have already submitted a feedback to mozilla but got no response. 

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

mconnor has been planning changes to the search service update system that would allow search providers to update the app-shipped engines. Part of the benefits for doing that would be the possibility of serving locale-specific updates such that users would go directly to their localized version of the search engine.

Comment 2

[:Gavin Sharp [email: [e-mail]]]

Er, why did you resolve this as FIXED?

Comment 3

[Jeferson Hultmann]

(In reply to comment #0)
Unfortunately, localizations are not allowed to provide a localized Google plugin. All people outside US are redirected to local domains.

Comment 4

[Mike Connor [:mconnor]]

This originally was done at the request of Google, FWIW.  The problem was that in many cases locale is not a good match for location (i.e. we serve en-GB for English users in .au, hardcoding co.uk is actually far worse for those users).  There's also a very large number of people using en-US builds in different locations that are better served by a different TLD.

We're working on a change for 3.1.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to comment #4)
> This originally was done at the request of Google, FWIW.  The problem was that
> in many cases locale is not a good match for location (i.e. we serve en-GB for
> English users in .au, hardcoding co.uk is actually far worse for those users). 
> There's also a very large number of people using en-US builds in different
> locations that are better served by a different TLD.
> 
> We're working on a change for 3.1.

Mike, any update on your last comment? Has something been changed for 3.5 in this area?

Comment 6

[Mike Connor [:mconnor]]

bug 467890 covers the support in Firefox, I don't know when we'll have a default google search plugin checked in, but that's in progress, if not already done.