Display get corrupted when you scroll with up/down arrows with gtk/linux port of mozilla. You can for example press up/down arrows on bugzilla page and create so bad display corruption that it is hard to enter values right. Pavel

Updating QA Contact

Tom -- another one you've seen before

Bug is there even in M6/Linux release. You can either press up/down or pgup/pgdn, both are enough to reproduce this bug on any simple page.

See bug 8565. Could the problem have something to do with painting twice?

Bug 8565 seems to explain why this is happening. Now you just need to explain bug 8565. Probably one of these should be resolved as a dup of the other, but I'm not doing it because I don't know who should deal with the problem.

Marking [PP] since this seems Linux-only. Correct me if I'm wrong.

Bug #7354 seems to be fairly similar, you might want to take a look.

just wondering : is this bug still new ? I see the same behaviour in m8 and 1999-08-11 source compiled on my machine. It happens when I click in the trough of the scrollbar (scroll by page), on large pages such as the famous http://www.w3.org/TR/REC-CSS1. When you reach the middle of the page, lines of text are written accross one another, and it becomes unreadable. I also noticed when I load large pages I get lots of these messages on the console : FindShortcut: in='http://www.w3.org/TR/REC-CSS1' out='null' Block(body)(1)@0x855b520: WARNING: desired:8265,502425 nsBlockReflowContext: Block(body)(1)@0x855b520 metrics=8265,502425! Area(html)(-1)@0x82d6f68: WARNING: desired:9555,503385 Block(body)(1)@0x855b520: WARNING: desired:8265,510952 nsBlockReflowContext: Block(body)(1)@0x855b520 metrics=8265,510952! Area(html)(-1)@0x82d6f68: WARNING: desired:9555,511912 Block(body)(1)@0x855b520: WARNING: desired:8265,519717 nsBlockReflowContext: Block(body)(1)@0x855b520 metrics=8265,519717! Area(html)(-1)@0x82d6f68: WARNING: desired:9555,520677 Block(body)(1)@0x855b520: WARNING: desired:8265,527643 etc...

This was fixed a while back. Marking dup of bug 7354. hrenault@pratique.fr : What you are describing sounds like a separate bug. In fact, it sounds just like bug 1177, which was marked fixed well before your report. Perhaps it needs to be reopened. However, you don't say what platform you are on, so the report isn't very helpful. *** This bug has been marked as a duplicate of 7354 ***

Marking as verified duplicate of 7354.