575184 - Some windows show before size is properly set

Status: RESOLVED FIXED

(Core :: Widget: Win32, defect)

Description

[Bas Schouten (:bas.schouten)]

Since landing bug 513162 the structure of widgets has changed. This causes premature show events to sometimes occur before the window's size and positional parameters are properly set. This causes an effect of briefly seeing the window in a wrong position before it moves to the correct one. The majority of this was fixed in bug 574690 but for some windows this still happens (for example the Library window (Ctrl + Shift + B)).

Comment 1

[Jim Mathies [:jimm]]

Presumably you're more in the mood to work on D2d bugs Bas, so I can take this? ;)

Comment 3

[Jim Mathies [:jimm]]

resolved rixed by bug 574690.

Comment 4

[Jim Mathies [:jimm]]

*fixed!

Comment 7

[Matthias Versen [:Matti]]

not fixed  with Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3pre) Gecko/20100726 SeaMonkey/2.1a3pre and the last dupe is for 4.0b2 which is Gecko/20100720

Just opening a new window and I can see a new window that changes the size in my case to maximized. It doesn't change the size if you don't use a maximized window

Comment 8

[Jim Mathies [:jimm]]

(In reply to comment #7)
> not fixed  with Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3pre)
> Gecko/20100726 SeaMonkey/2.1a3pre and the last dupe is for 4.0b2 which is
> Gecko/20100720
> 
> Just opening a new window and I can see a new window that changes the size in
> my case to maximized. It doesn't change the size if you don't use a maximized
> window

Hey Matthias, could you provide specific steps to reproduce?

Comment 9

[Matthias Versen [:Matti]]

1) open FF/SM trunk
2) resize a not maximized window to a small size
3) maximize the window with the button at the title bar
4) press ctrl+n
5) a new window opens but it seems to open in a not maximized size and it will immediately resize to a maximized state.
You get the same affect at the initial SM/FF start if you have a maximized window position saved.

opening a new FF/SM window from a not maximized window doesn't show a resize. It opens in the correct size.
The resize effect is the the same resize effect that you get if you manually maximize a window.

Comment 10

[Jim Mathies [:jimm]]

(In reply to comment #9)
> 1) open FF/SM trunk
> 2) resize a not maximized window to a small size
> 3) maximize the window with the button at the title bar
> 4) press ctrl+n
> 5) a new window opens but it seems to open in a not maximized size and it will
> immediately resize to a maximized state.
> You get the same affect at the initial SM/FF start if you have a maximized
> window position saved.
> 
> opening a new FF/SM window from a not maximized window doesn't show a resize.
> It opens in the correct size.
> The resize effect is the the same resize effect that you get if you manually
> maximize a window.

Technically not this bug. You might file off a new one in widget.

FWIW, I'm not able to reproduce in Fx on trunk.

Comment 11

[Matthias Versen [:Matti]]

in that case marking again as fixed and sorry for the noise

Comment 12

[Satish]

I updated just to to Firefox 4.0b3 and I am still having this issue. When I open the Firefox for the first time or when I open a new window (Ctrl+N), I could able to see "literally" the Firefox being resized couple of times before coming to the maximized mode.

Platform: Windows XP SP3.

Comment 13

[Nick Betcher]

(In reply to comment #11)
> in that case marking again as fixed and sorry for the noise

This has not been fixed entirely in 4.0b5... the window starts maximized, then resizes to the size the page requested. For computers with lower-end graphics cards the resize event takes a good 200ms to complete.

Comment 14

[Jim Mathies [:jimm]]

(In reply to comment #13)
> (In reply to comment #11)
> > in that case marking again as fixed and sorry for the noise
> 
> This has not been fixed entirely in 4.0b5... the window starts maximized, then
> resizes to the size the page requested. For computers with lower-end graphics
> cards the resize event takes a good 200ms to complete.

Do you have steps to reproduce or a test case? Are you talking about popups maybe or the main fx window?

Comment 16

[Matthias Versen [:Matti]]

re comment #10: filed bug 582755 (and I can see the problem in FF4b5)

Comment 17

[Nick Betcher]

(In reply to comment #14)
> Do you have steps to reproduce or a test case? Are you talking about popups
> maybe or the main fx window?

https://bugzilla.mozilla.org/show_bug.cgi?id=577169