From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5+) Gecko/20011110 BuildID: 20011110 At the page, http://sports.espn.go.com/mlb/players, if you try to enter information into any of the 3 input boxes on the page, there is a very long pause between displaying each letter that you inputted. While the browser is displaying each letter that was typed, you can't scroll the page or click on any links. Reproducible: Always Steps to Reproduce: 1. go to http://sports.espn.go.com/mlb/players 2. try to type in the text boxes to search for a player by last name or the search on the left 3. watch as the browser stops responding as the text you typed is slowly display Actual Results: Browser takes a long time to display each character. Expected Results: The browser to display them as they are typed. I have the same problem in linux on a newer build, 20011114, but it's not as bad. Still very noticeable, but not as bad.

No dupes found. Confirming and marking NEW (2001111503 on Win2k).

->

Here's a reduced test case based on the http://sports.espn.go.com/mlb/players page. The slow down seems to be caused by the interaction between the body's background image (which is a very wide but short image, containing a run of white pixels, followed by transparent pixels followed by some blue pixels) and the Advertisement image in the absolutely positioned div of the right sidebar. Typing speed is restored to normal if I do one of the following: 1. Remove the background image from the body. 2. Remove the image from the absolutely positioned div. 3. This is a bizarre one ... remove the space between "</div> </div>".

Turns out you don't need the Ad image to reproduce this. I also figured out that the whitespace between the 2 </div>s may be significant since it adds an extra line to the absolutely positioned div in the frame tree.

--> 0.9.8

Adding keyword testcase since this has one.

Theres another bug about a single whitespace character turning a normal page into something really slow but I can not find it now.

Performance in the reduced test case and http://sports.espn.go.com/mlb/players are fine using 2002031803 build on WinXP on a 750Mhz AMD processor. I think the performance issue was corrected when dcone@netscape.com checked in a performance fix for tiled background images

Resolving WFM.

Hmmm, I still see this on my 450Mhz PII running WinNt4 sp5. I can definitely type ahead of the rendering when visiting the page on espn.com and with the test cases above.

adt3 per adt triage

nsbeta1-. Engineers are overloaded with higher priority bugs.

This might have something to do with Bug #119318

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