282998 - No "resize" event is sent if Mozilla starts up in maximized mode

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Manuel Reimer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7.3) Gecko/20040910 Mnenhy/0.7.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a6)

I register an event listener like that in an overlay on navigator.xul:

window.addEventListener("resize", ResizeHandler, false);

In Mozilla up to 1.7.5 I always got an resize event if mozilla starts up, so
this was the right place to rearrange the window items of my extension. Since
1.8a5 I not longer get this resize-event everytime. I only get it if the window
is in "normal" state.

Reproducible: Always

Steps to Reproduce:
register an resize-event as mentioned above in the context of the navigator
window. Then restart mozilla after maximizing it. After restart you won't get
your event.

Actual Results:  
I can't use "resize" anymore to rearrange my window items. It would be possible
to do this on the "load" event, but this would cause the window to be redrawn
twice if the window is in "normal" state.

Expected Results:  
Mozilla should send "resize" everytime to tell the extensions to rearrange their
buttons.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Shouldn't you be using a load listener instead?

Comment 2

[Manuel Reimer]

All other "window systems" I know also send a resize at startup. So the code to
arrange the window items only has to be held in one place.

As mentioned in the description the window items would be arranged twice while
startup if I use the load listener and the window is not in maximized state.

The major problem is the different behaviour if the window is maximized or in
normal state.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.