If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Search sidebar rebuilds list when I navigate back to search results

RESOLVED EXPIRED

Status

SeaMonkey
Search
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Zac Jacobson, Unassigned)

Tracking

(Blocks: 1 bug, {helpwanted})

Trunk
x86
Windows 2000
helpwanted

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
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.

Comment 1

16 years ago
Also seeing this with 2001101021/Redhat 7.1

Comment 2

16 years ago
I believe this is Search component.
Component: Sidebar → Search

Updated

16 years ago
QA Contact: sujay → claudius

Comment 3

16 years ago
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.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Sidebar display search results gets rebuilt too often → Search sidebar rebuilds list when I navigate back to search results

Updated

16 years ago
Priority: -- → P2
Target Milestone: --- → mozilla0.9.7

Comment 4

16 years ago
Moving to mozilla0.9.8.
Target Milestone: mozilla0.9.7 → mozilla0.9.8

Updated

16 years ago
Target Milestone: mozilla0.9.8 → mozilla0.9.9

Comment 5

16 years ago
Search triage team: -> Future
Keywords: helpwanted
Target Milestone: mozilla0.9.9 → Future

Updated

15 years ago
Depends on: 172122

Updated

15 years ago
Blocks: 172122
No longer depends on: 172122
(Assignee)

Updated

9 years ago
Product: Core → SeaMonkey
Assignee: samir_bugzilla → nobody
Priority: P2 → --
QA Contact: claudius → search
Target Milestone: Future → ---

Comment 6

8 years ago
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

Comment 7

8 years ago
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.