127540 - Previous results displaying in sidebar before showing the current one

Status: RESOLVED EXPIRED

(SeaMonkey :: Search, defect)

Description

[Erich 'Ricky' Iseli]

Steps to reproduce:
1. use the sidebar to do a search on any engine, say Google for searching "lizards"
2. the results display in the sidebar as well as in the browser.
3. switch engine in the sidebar, let's say to dmoz.
4. Click on search again

Results: the results first shown are the results from google. If you wait long
enough, the results get changed to dmoz.

Very often, users get confused because the changes don't seem to have been
considered (the user switched engine but yet, the previous engine is being used).

Comment 1

[Samir Gehani]

What is the behavior you would expect?  Spending cycles to clean out the
previous list seems futile.  

Comment 2

[Erich 'Ricky' Iseli]

I forgot to mention that we are in advanced search mode. So switching search
engines means that you put away the results and see a list of search engines.
Then when you click on search again, you see the old results again, which is
confusing.

Mark it Future, but not won't fix because this makes it feel really unstable and
not smooth.

Comment 3

[Samir Gehani]

-> Future, helpwanted

Comment 4

[Robert Kaiser]

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

Comment 5

[Robert Kaiser]

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