we need to come up with a real solution to this problem. The current hackery that is in the body frame code doesn't work anymore and consequently we are going to be wasting alot of cycles painting too much. What I suspect we need to do is to make each of the container layout classes call Invalidate with the right damage area based on what they did...

This is not my bug. If you remember, I've been saying for a while that each of the frame classes needs to handle its own repainting. The block and table code are two of the biggest offenders...

Well then let rick assign it. :-(

this is a layout bug.

Setting all current Open/Normal to M4.

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

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

Something has regressed here over the past few days. In builds from last week, mousing over a toolbar button did not cause the entire window to redraw (this was fixed for the first time a few weeks back). But a build from today is showing entire-window reflow/redraw again, when mousing over a button.

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

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

Some progress on this. We defined how it should work and the block code has been changed to do damage repair during an incremental reflow. Leaving open because the table code still needs to be changed

Table code has been changed to be incremental

Based on troy's comments, marking as verified fixed in the Oct 1 build.