Closed Bug 161534 Opened 22 years ago Closed 14 years ago

When select multiple engines, different search result order between sidebar and Navigator.

Categories

(SeaMonkey :: Search, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kasumi, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

tested on 2002-08-06-09-1.0
Mac OS X JA

1. CheckS Advanced in Preference/Navigator/Internet search
2. On sidebar/Search tab, select all Engins
3. Check maltiple engines, e.g. Music:... and Google
4. Type any in inputbar on Sidebar/Search tab
5. Click Serch button
6. In Sidebar, result order is by engine
   In Navigator, result order is by alphabet  
   Please refer attachment
  
Expect: synclonize default result order between sidebar and Navigator
Attached image screen capture
Summary: When select maltiple engines, different search result order between sidebar and Navigator. → When select multiple engines, different search result order between sidebar and Navigator.
Depends on: 172122
Blocks: 172122
No longer depends on: 172122
Product: Core → SeaMonkey
Assignee: samir_bugzilla → nobody
QA Contact: claudius → search
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: