53587 - Persistent search results keep reloading

Status: VERIFIED DUPLICATE of bug 51211

(SeaMonkey :: Search, defect, P1)

Description

[Michael La Guardia]

Steps:
1)  Type in a series of terms into the location bar.  I used "greyhound rescue".
2)  Hit return.

Expected result:  Search page loads, Search Sidebar tab opens and displays list
of results.

Actual result: Search page loads, but the sidebar tab keeps loading and
reloading an additional 5 to 10 times.  Even if you open another tab, the search
tab will pop up again with a new reload.  Extremely confusing and annoying.

Using 2000092108 on NT.

Comment 1

[Michael La Guardia]

Nominating for nsbeta 3.  This is a major problem with high profile functionality.

Comment 2

[don]

Marking "nsbeta3+".  I have to agree with LaGuardia on this.  Matt says he saw
this happening in yesterday's build.  He's bugging rjc for help ...

Comment 3

[matt]

rcj thinks this is a tree widget problem.  I did some debugging
and saw that it looks during the reload of the frame to checkForDirectoryListing
in navigator.js and remembersearchText in search-panel.js .
I'm giving it to him to see if he knows more.

Comment 4

[Robert John Churchill]

(Yep, apparently not a <tree> problem at all!)

In navigator.js around line # 425 you'll see that the content area gets various 
load listeners added to it, such as:
   contentArea.addEventListener("load", UpdateInternetSearchResults, true);

The problem is that these are firing several times per page load (which of course 
happens to screw up the search sidebar results panel;  it also slows down the 
browser in general because a lot of extra work is being done).

Who fires these, the docshell maybe?  Matt, can you find out and assign this bug 
to whoever works on it?

Comment 5

[matt]

this is either a sherlock file problem
or a server problem
Either way rjc will know better

Comment 6

[Robert John Churchill]

[This is neither a Sherlock file problem or a server problem... see above 
comments.  :) ]

Who fires these, the docshell maybe?  Matt, can you find out and assign this bug 
to whoever works on it?

Comment 7

[don]

Robert,

Right now Matt is way overloaded.  We're asking for your help because he hasn't
been able to figure this out.

Comment 8

[Robert John Churchill]

Don, yes, I know... and I looked into it a bit. Now I'm asking for your help... 
*please* assign this to someone who works on the docshell so they can 
investigate why multiple "load" events are being fired.  :)

Comment 9

[don]

Adam, can you help us out here?  (See previous comments.)

Comment 10

[Adam Lock]

There has been a historical problem with onload being fired too early when 
progressive layout is enabled.

Wasn't it enabled recently?

Comment 11

[don]

Not sure.  Who would have made this change anyway?

Comment 12

[Adam Lock]

Looks like a dup of bug 51211. Images in the search results page may be firing 
onload events which the search onload handler is being called to handle.

*** This bug has been marked as a duplicate of 51211 ***

Comment 13

[Blake Ross]

i agree. vrfy dup, and will be sure to recheck this once 51211 is fixed.