Closed Bug 224120 Opened 21 years ago Closed 20 years ago

Advanced Search in Search Sidebar does not remember chosen engine

Categories

(SeaMonkey :: Search, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 206464

People

(Reporter: jnareb, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031016
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031016

The Search Sidebar in advanced mode (i.e. when one can select the category of
search) does not remember chosen (checked) search engine. This may be not
reproductible, as on another machine with Mozilla 1.4 this problem does not
appear. I had this problem with Mozilla 1.4 from the Linux distribution Aurox
9.1, then upgraded to Mozilla 1.5 from ftp.mozilla.org yum RPM packages

http://ftp.mozilla.org/pub/mozilla.org/mozilla/yum/SeaMonkey/releases/current/redhat/i386/

(there is no mozilla-nss RPM with SSL support for Mozilla on this site) and I
have the same problem.

What is suprising copying search.rdf from backup from Mozilla 1.4 does not work...

Reproducible: Sometimes

Steps to Reproduce:
0. In "Preferences/Navigator/Internet Search" select "Advanced"
1. Select Search sidebar tab
2. Select one of engines
3. Select other sidebar tab
4. Return to the Search sidebar tab

or 

3. Select other search category
4. Return to previusly selected category

Actual Results:  
The selection disappears. None of Serach Engines is selected (checked).

Expected Results:  
Mozilla should remember chosen Search Engines per category.

This bug appears also with the clean, freshly created profile.
Extensions used: MozTweak-1.2.1, MultiZilla v1.5.0.3, GoogleBox v1.3, Linky-2.0.0.
Happens also in my machine:
	
Mozilla 1.7b
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316

*** This bug has been marked as a duplicate of 206464 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.