Closed Bug 291240 Opened 20 years ago Closed 18 years ago

in the tool bar seach i use google when i type a word it then seacher in singapore when my home page firefox is set in Australia

Categories

(Firefox :: Search, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: wadie, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

my home page is set to
http://www.google.com.au/firefox?client=firefox-a&rls=org.mozilla:en-US:official
so when i seach in this window i get Auzzie sites.

But when i use the side seach (quick seach) i get singapore 


Reproducible: Always

Steps to Reproduce:
1.use the side seach or go seach
2.type the word coolpc
3. then this window comes up
http://www.google.com.sg/search?q=coolpc&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:officia
 

Actual Results:  
as you can see it has a singapore seach
when my home page is set to 
http://www.google.com.au/firefox?client=firefox-a&rls=org.mozilla:en-US:official

Expected Results:  
just gone to this page instead
http://www.google.com.au/search?client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial_s&hl=en&q=coolpc&meta=&btnG=Google+Search
or may be i'm wrong you tell me
Do you get also the singapore version if you open http://www.google.com ?
yes i do when i type in www.google.com
How come your home page is set to google.com.au in en-US build?

And what is "the side seach or go seach"? The (google) search bar at the top-right?
Assignee: bugs → nobody
Component: Toolbars → Search
QA Contact: bugzilla → search
Under your firefox folder, you should find a searchplugins folder.  The .src
files here define the rules for the search box.  Take a look at google.src. 
What is the "action" URL?
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.