93609 - Problems drawing a window when double clicking on turbo icon in system tray

Status: RESOLVED FIXED

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

Description

[yeckel42o]

It has started with the resend builds in late june i double click on the little
mozilla icon and the winoow pops up in the top left with just floor/max/close as
options it dose not seem to fully draw its self and get stuck. If i turn the
turbo load off and start with the spalsh screen it seems to be ok also
respawning of windows seem to be slower now that might be a whole other bug tho :)

Comment 1

[Dan Hartung]

I see similar behavior with 2001090703. Double-click doesn't always work, for
one, but when it does the first thing that happens is this tiny stub window just
big enough for the title bar and the control boxes (system, min, max, exit). 
After a second, the main Mozilla window opens, except once it was stuck on the
stub window. Other times the full size window opens, but it doesn't draw its
borders properly. You can see the border where the stub was, that's all, even
though the other window features (title, menu, scroll bars, etc.) are where
they're supposed to be; there's a blank space (showing whatever's behind) where
the border should be. It's just this outer border that's not redrawing when the
stub expands to the main window.

Comment 2

[Michael Kaufmann]

Attachment: Screenshot showing the bug (it looks like BeOS!)

Comment 3

[Asa Dotzler [:asa]]

worksforme with 092003 win98 and win2K mozilla trunk builds

Comment 4

[Ryan Pertusio]

I have indeed seen this on build 20010918, using WinME, but have not seen it on
more recent builds.  However, this doesn't mean the problem is gone.  I have
noticed too that the problem appears at random.  I'll be sure to add more
comments if I can get the problem to surface again.

  Should this be added to the dependency/blocker list of bug 75599?
I have removed bug 99488 from the "blocks" list, because it is a duplicate of 75599.

Comment 5

[Asa Dotzler [:asa]]

not sure who should get this. shotgun reassign. 

Comment 6

[Peter Trudelle]

I'm not sure this should even remain open, let alone added to 75599.  Unless
someone can repro using a recent build, it sounds like it should be resolved
WFM.  FWIW, I don't see it on Win98

Comment 7

[Michael Kaufmann]

I still see this bug on build 2001092003 (on Windows 98 SE).

To reproduce it, double click on the quickstart icon, close mozilla, double 
click on the icon and so on until you can see the bug. (You should not maximize 
your mozilla window.)

You can also try to click three or more times on the icon. Click quickly while 
the mozilla window is loading.

Comment 8

[Michael Kaufmann]

--> QuickLaunch

Comment 9

[Michael Kaufmann]

Attachment: Screenshot: This time only the window borders are missing

Comment 10

[Grace Bush]

Saw this on Win95 today- N6 build

Comment 11

[Ryan Pertusio]

  Yes.. in regard to my post above, I HAVE seen this happen today, on build 0927
on WinME.  Actually, it happened twice.  The first time showing Michael's first
screenshot (the original bug description), and then a few hours later showing
Michael's second (most recent) screenshot.
  I'm playin with different settings, procedures, programs, memory
configurations (and other variables) to see if I can pinpoint the exact
circumstances that it happens (to aide bug fixers).  So far, I can't pinpoint
anything :(  It's a "random" bugger, I think.
  ** still investigating **

Comment 12

[Michael Kaufmann]

You should be able to reproduce this bug with the following steps:

1) Make sure that the Mozilla window isn't maximized
2) Close the Mozilla window
3) Click four times on the Mozilla tray icon (make a double-double-click!).

Then the Mozilla window appears and it looks like screenshot 1 or 2.

Comment 13

[Blake Ross]

Can someone retest this please? Law's fix may have fixed this.

Comment 14

[Michael Kaufmann]

I think that the fix for bug 103849 has fixed this bug too. Now two windows are
opened if you make a double-double click on the tray icon. That's how it should
be (tested with build 2001101803).

It could be possible that this bug still appears at random. But I guess that
it's really fixed now.

Comment 15

[Blake Ross]

Marking fixed.