From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.1+) Gecko/20010608 BuildID: 2001060804 <select> that has multiple possible options, but does not have enough <option>s to fill it can have garbage painted on it when scrolling past and back to it. Reproducible: Sometimes Steps to Reproduce: 1. Load page with aforementioned prerequisites 2. Scroll down 3. Scroll back up 4. If nothing happens, try again Actual Results: Garbage from other parts of the page is painted in the non-selectable part of the <select> Expected Results: No garbage should have appeared.

*** Bug 85042 has been marked as a duplicate of this bug. ***

*** Bug 85051 has been marked as a duplicate of this bug. ***

Confirming: I see this on WinNT 2001 061104, and several of the dups were already in the NEW state.

For clarification, I see this on show_bug.cgi about 40% of the time. I've also noticed that the elements in <selects> are closer to each other than they should be.

It is possible that garbage always gets dumped in it, it just doesn't show because the garbage happens to be the white background at the time. Also the select box size problem I mentioned in bug 82265 and may have resulted from the patch for bug 82626.

Damn mid-air-collisions... What I was trying to say was, "scroll upwards slowly to see the effect best."

I think this was fixed by the back-out of the fix for bug 82626

*** Bug 85609 has been marked as a duplicate of this bug. ***

Reassigning to Rod.

This bug is back again.. WinXPRC2/2001081403-trunk oddly enough bug 82626 is gone again...

okay this regressed, but it doesn't have anything to do with bug 82626

This is really bad with build 2001081716 on Win2k (SP2). on bugzilla pages, I am seeing the back/forward buttons and/or home and bookmarks toolbar links (right below back/forward buttons) covering the cc: list. Steps to reproduce: 1. reload this page 2. scroll the page down so as to just cover up the cc: list 3. scroll back up. You should now see what I described above displaying in the cc: list This has got to have a better target than 1.0 and a higher priority than normal! jake

Confirming for 2001083106 linux, nominating for 0.9.6 It's annoying if you work often with bugzilla

Interesting note to this - it is also happening on the 0_9_2 branch post 6.1, so whatever broke it on the trunk was put on the branch as well - might narrow it down.

Although this bug is the older one - This one is already assigned : *** This bug has been marked as a duplicate of 95703 ***