From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5+) Gecko/20011012 BuildID: 2001101203 If you follow a link on the search results page, and then use the browser's back-history button, the sidbar reloads the search results. This shouldn't be necessary, especially since building the sidebar version of the search results seems computationally intensive, and bogs down the browser. Reproducible: Always Steps to Reproduce: 1.Enter a fairly common term in the search text field. "Java" for instance. 2.Hit the search button. Notice that the browser is unusable for a moment as the sidebar search results list is built. 3.Follow a link to any bug frome either the sidebar or the browser. 4.After viewing (and perhaps fixing) that bug, hit the browser's "BACK" navigation button. Actual Results: The browser bogs down as the sidebar search list is re-constructed, even though the search results should not have changed. Does Mozilla resubmit forms when navigating through the history? Expected Results: The search list should be displayed in the browser again, but the search list should not have to be reconstructed. The browser should not bog dowdn when constructing this list.

Also seeing this with 2001101021/Redhat 7.1

I believe this is Search component.

The slowness is bug 77460. This bug should be fixed even if 77460 takes care of the performance problems, because this bug also causes the list to scroll to the top when you navigate back to the search results page.

Moving to mozilla0.9.8.

Search triage team: -> Future

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

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