245428 - Default behavior of search bar after fresh install (new profile) is Find in This Page, not Google (installer only)

Status: RESOLVED WORKSFORME

(Firefox :: Search, defect, P4)

Description

[Tim Meader]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040529 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040529 Firefox/0.8.0+

Basically, the search bar should default to a state usable for web searching,
not for searchinng in the same page. Most people are extremely used to just
going to Edit->Find in the Page, if they are coming from IE. The immediate
usefullness of having a seperate, always on, box for doing "Find in Page"
searching wouldn't be too clear to a new user. However, having an always
available Google searching box would be beneficial. Thus, it makes a little more
sense to default the search bar to Google.

Reproducible: Always
Steps to Reproduce:
1.Install Firefox (installer build, new profile)
2.Observe the default behavior for the search bar
3.

Actual Results:  
It was set to Find in Page

Expected Results:  
Should (in my opinion) default to Google

Comment 1

[Ali Ebrahim]

Setting blocking1.0? so that someone empowered can decide on this.

Comment 2

[Ross Kendall]

Not sure if I agree this is a bug,  however I can confirm that I get the same
behaviour on this installer build (and the day before):

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040602
Firefox/0.8.0+

Comment 3

[u60234]

Confirming bug with installer build Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-US; rv:1.7) Gecko/20040604.

This is yet another bug that only show up in the installer builds, but not in
the zipped builds.

Bug 214528 made Google the default search.

Comment 4

[Hussam Al-Tayeb]

when starting a new profile, the js console gives a search.xml error. Could 
this be related?

Comment 5

[Tim Meader]

This is WFM on the official installer. Anyone else confirm?

Either way I'll likely close this later today.

If you are experiencing anything else mentioned in this bug, but NOT the Google
problem, please open a new one.