The Component may or may not be set correctly (difficult to pick any component in that list). Steps to reproduce: In Editor, choose Insert Image and then resize the window. Notice that portions of the parent window appear in this window after each resize.

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

It looks more like a problem with offscreen buffers being re-used by the ViewManager, rather than a problem with grafport clipping or setting. I'm not changing the Summary line though since it's a good description of how a "normal" user (not you Kathy ;-) may perceive the bug.

pierre may be able to get to these before M7 ends but I also saw this... "I'm on vacation this week. I'll be back at the office Monday June 14th (weather permitting)." moving to m8 for now

Fix checked in for M7 on Wed 06/16 at 9pm. Four bugs were related to each other and fixed at the same time: 3455: [PP] mac/linux, dual toolbars appear after surfing. 6989: Multiple window drawing gets messed up. 6678: [PP]clipping/port problems in child dialogs. 5560: [PP] CornerView displays garbage.

Fixed in the June 17th Build (1999061708)

reopening this bug; I still see this problem with editor dialogs

Clearing Fixed resolution since the bug is now Reopened.

rolling over to m8

Correct, we still have some problems although they seem to only be clipping problems now (with some areas which are left blank), not drawing problems (with some text from another window showing inside the dialog). Reassigning to Don Cone.

The clipping issue is still reproduced in the Mac June 28th Build.

This is blocking my work in dialogs. Can we get a fix to it soon? Is it cross-platform?? I heard a rumor that this might be a problem on Linux as well...

cc sfraser@netscape.com

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

I have a fix for this. The problem occurs in nsWindow::HandleUpdateEvent(), because the origin in the windowPtr is not (0,0) when handling the update event, and so the damagedRgn is in a different coordinate space from the updateRgn. Thus the ::SectRgn(damagedRgn, updateRgn, updateRgn); intersects regions in different coordinate spaces. The fix is simply to add a SetOrigin(0,0) just before that SectRgn call.

I checked in the fix to mac/nsWindow.cpp

Yes !!!. It is fixed in the Mac August 3 Build. Good job, Simon !