From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.3) Gecko/20010801 BuildID: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.3) Gecko/20010801 I've got a Matrox G400 with dual head, but I usually disable dual head. Ever since I downloaded and installed Moz 0.9.3 and enable dual head, use a Moz window on my second monitor, then close it there, then disable it afterwards, when I minimize Mozilla after disabling DH, I get just the left part of the Mozilla screen sticking out on the right side of my prime monitor. I can't move it from there either, just maximize it again (luckily ;-)) A picture can be found at http://home.planet.nl/~elst0093/errm.jpg When I maximize this window again, I cannot type in any of the answerboxes on Bugzilla, or any of the other boxes on other sites anymore, not even after quiting Moz and restarting it. I have to reboot. Reproducible: Always Steps to Reproduce: 1. Use Mozilla 0.9.3 Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.3) Gecko/20010801 2. Start DualHead on a Matrox G400, using drivers 6.51, WinME, and move at least one of the Mozilla windows over to the other monitor. Quit it there before step 3. 3. Quit DH by disabling the second monitor in Powerdesk. 4. Either use the Mozilla window you're using or open up a new one, and try to minimize it. Actual Results: In my case it will end up like in the picture above. Expected Results: I expect it to minimize on my primary monitor.

sounds like xptoolkit to me, reassigning to owner and qa contact of xptoolkit

disabling a monitor while the app is running is like waving a red blanket in front of an angry bull ;) i'm sure mozilla just isn't noticing the change of monitor setup (i think we cache the monitors). perhaps there's a win32 event that we should be watching for to invalidate said cache, but this is hardly high priority. workaround: don't do that ;)

May God have mercy on us all. The 212 bug spam-o-rama is Now!

fffffffuture

I don't think the submitter is disabling a secondary monitor when Moz is running - he says closes it after the Moz window is in the secondary monitor. I tried reproducing this in various different ways: disabling the secondary monitor both with Moz running and after stopping Moz with the last window closed on the secondary screen. In call cases I was unable to get Moz to do anything except what I expected (ie: show the new window on an adjacent monitor until it was all visible). It worksforme in Moz 1.4, shall we mark this one as fixed?

Reporter, please try this again with a new build. If all is well, please change your bug's resolution to WORKSFORME.

I must say, I haven't tried it on my new Radeon 9600 Pro yet, but then again, I am a monitor short. So will change the assertion to WFM. Thanks for the reminder.