User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Please see the URI for a test case. Load the document and using the scrollbar quickly scroll down to the bottom of the page. Then scroll back up slowly. Usually you will see a few black lines appear between table rows.
I can reproduce this on Windows XP and also on a different machine running Fedora Linux 8. I will attach two screenshots.
Interestingly if you remove the heading and text before the table, the bug doesn't show.
Steps to Reproduce:
1. Load the document.
2. Scroll down to the bottom.
3. Slowly scroll back to the top using the scrollbar.
1-pixel-wide black lines appear between random table rows, as shown in the two screenshots.
The display should not be altered by scrolling down and then back.
Might possibly be the same bug as #283229. The other 'horizontal lines' bugs are not specific to table cells. I don't see random horizontal lines in other places, only between the rows of this table when scrolling.
Created attachment 313580 [details]
Screenshot of the test case page on Linux Fedora 8 after scrolling
Created attachment 313581 [details]
Screenshot of the test case page on Windows XP after scrolling
One more note - I am using Firefox 3 beta 5, binary download, on both Windows and Linux.
Created attachment 313582 [details]
HTML for test case
Attaching the HTML in case the web site referenced goes down.
Also see bug 426842
Confirmed on Windows XP. It is a regression between 20021029 and 20040210 and the first build was a release (Phoenix 0.4).
This still occurs with 3.0 rc1 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0).
This still occurs with 3.0rc2 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0).
This still occurs with 3.0 final (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0).
This still occurs with Shiretoko 3.1a1 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1a1) Gecko/2008072310 Shiretoko/3.1a1).
This still occurs with Shiretoko 3.1a2 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1a2) Gecko/20080829082037 Shiretoko/3.1a2).
I see this on Linux as well:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/2008070206 Firefox/3.0.1
OS/ Hardware --> All
This still occurs with Firefox 3.0.2 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:220.127.116.11) Gecko/2008091620 Firefox/3.0.2).
This still occurs with Firefox 3.0.3 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:18.104.22.168) Gecko/2008092417 Firefox/3.0.3).
Ed, no work has been done on this bug as you can tell by the fact that you're the only person commenting in it. Please stop spamming the bug unless you have something new to report. Random "this still doesn't work" messages don't help fix the bug.
Bernd, dbaron: Do either of you have an idea of what might be going on here?
typical Border collapse paint error
Just a note to say that this bug is also reproducible on the Mac - can the bug subject line be changed?
Ed - FWIW, this appears to be fixed on the trunk. I can't reproduce with a current mozilla-central nightly. Given that this was fixed between the 2009-11-04 and the 2009-11-05 nightlies, it's highly likely that it was fixed by the border collapse rewrite (bug 452319).
If you'd like to confirm this yourself, you can grab a nightly build and run it through the testcase in the bug. Note that you'll probably want to use a new profile for it as well.
It's a bit unclear at the moment which Firefox release will come next from mozilla-central, but whatever release that is will contain the fix for this bug.
>It's a bit unclear at the moment which Firefox release will come next from
>mozilla-central, but whatever release that is will contain the fix for this
3.6-rc1 appears not to contain the fix - does that mean these changes will not
be included until Firefox 3.7?
Correct, 3.6 branched off before this fix was landed on mozilla-central. It's still not certain what version of Firefox will be coming from mozilla-central next, though it appears these days that indeed it will be 3.7. Also, it's unlikely the patch that fixed this will be backported to 3.5.x/3.6.x since it was a large, complicated fix - not the kind that's typically taken into security/stability releases.
I'm pleased to report that this is now fixed (in Firefox 4 beta 1, Win32). Thanks to everyone who helped with this.