37315 - Search button has been Netscapized

Status: VERIFIED DUPLICATE of bug 30653

(SeaMonkey :: General, defect, P3)

Description

[Jason Heard]

I'm using M15 BuildID: 2000041811

In the preferences there are no longer options to search using Google, Yahoo, or
any other good search engine.  Also, the Search button doesn't match the UI any
more.  Will this be true from now on in Mozilla?  I thought it was independant
of Netscape.

Comment 1

[Gwyn Judd]

Yeah this definitely sucks. How about adding a text box in the prefs where you
can type in whatever URL you feel like?

Comment 2

[Brendan Donohoe]

Reassigning to German

Comment 3

[shuang (gone)]

It is a known bug. This might take bit longer to change or fix: it has something 
to do with how or whether the Search feature in the build can handle multiple 
search engineers in a stable manner. So be little patient with us and I am 
re-assigning it to the engineer who is working on this for future eveluation. 
Don, can you give to your team member?

Comment 4

[Ian Tommins ('thelem')]

There was also a special way that results were listed, in columns much like 
those in the inbox. I assume this is part of the same bug.

Comment 5

[Chris McAfee]

pref ui, search  -> ben

Comment 6

[Ben Bucksch (:BenB)]

> In the preferences there are no longer options to search using Google, Yahoo, or
> any other good search engine.

Bug 30653.

> How about adding a text box in the prefs where you
> can type in whatever URL you feel like?

With the search feature, we parse the result. We need "Sherwood" (IIRC) files
for seach engines. You can add them by clicking on an appropriate link (e.g. as
provided by your search engine provider).

> it has something
> to do with how or whether the Search feature in the build can handle multiple
> search engineers in a stable manner.

shuang, has this been resolved? If not, BenG is propably not the right person to
own this.

> There was also a special way that results were listed, in columns much like
> those in the inbox.

Bug 37875.

Is there something left? Or can we close this bug as DUP of bug 30653?

Comment 7

[Ben Bucksch (:BenB)]

> Is there something left? Or can we close this bug as DUP of bug 30653?

No answer, so I'll just do so. REOPEN bug 30653, if appropriate.


*** This bug has been marked as a duplicate of 30653 ***

Comment 8

[Matthew T (active 1999-2002)]

Verified dup.