* TITLE/SUMMARY [PP] Slowly expanding Apprunner window vertically leaves major bitgunk * STEPS TO REPRODUCE 0) Launch Apprunner 1) Shrink the *width* of the Apprunner window to the minimum window width. 2) Slowly increase the Apprunner window width about 10 pixels, and release the mouse button. * RESULT - What happened Throughout the rectangular region that comprised the resize region, many copies of the window border are left as bitgunk. Cleaning up this bitgunk requires a full window redraw (e.g. make background app, and then make foreground app again.) Doesn't affect vertical resizing, or shrinking of the window; only horizontal expansion. - What was expected No bitgunk left by resizing. * REGRESSION - Occurs On Win32 Apprunner (4.26.99 AM optimized build [NT 4, Service Pack 3]) - Doesn't Occur On Linux Apprunner (4.26.99 PM optimized build) Mac OS Apprunner (4.26.99 PM optimized build) Win32 Communicator 4.5 (RTM) * CONFIGURATIONS TESTED - [Mac] Power Mac 8500/120 (233 Mhz 604e), 64 MB RAM (VM on; 1 MB of VM used), 1024x768 (Thousands of Colors), Mac OS 8.5.1 - [Win32] Vectra VL (233 Mhz P2), 96 MB RAM, 800x600 (True Color), NT 4.0 SP3. - [Linux] Vectra VL (266 Mhz P2), 96 MB RAM.

reassigned to danm as p4 for m7.

Still happening 15.Jun.99. Why this is _my_ bug, and not someone in Layout's, I have no idea. But I'll look at it more closely later. Not today, though. It's a minor bug. Postponing.

mass-moving all m12 bugs to m13

giving me rest of phillips open qa contact bugs, sorry for spam

I wrote this one and will be able to most easily verify it when appropriate; qa assigning to self.

Rude of me to reassign this bug after it's been sitting in my lap for eight months. But here goes. Hey Eric -- this is clearly not a *window* bug; it's something in layout. The problem is, if you horizontally shrink the browser window until it's narrower than the menubar, the content area won't refresh when you size the window wider, until you've once again extended past the menubar. This seems to be Windows-specific. I'm thinking it might be a box thing, but only on general principle. Feel like taking a look?

moving to m15

fixed

This looks better, but still occurs in the Sidebar (specifically, in the content region of the active panel, which was 'News') using this morning's Windows build. evaughan, please let me know if you'd like me to split that into a separate bug report, or if it's still the same underlying issue.

Mass-moving most M15 bugs to M16

moving to M18

*** This bug has been marked as a duplicate of 33799 ***

Verified this bug as a duplicate of bug 33799 and marking as such.