288478 - when a window is being resized, none of its contained intervals and processes do not execute and onResize doesn't fire repeatedly

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[cdbarlow]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

When the window is being resized, none of the window's javascript code is
executed. This is most apparent with setInterval and setTimeout. I have a few
intervals running in the background, but when the window is being resized, the
intervals aren't fired so the timing in a game that I am writing goes out of sync.

In Internet Explorer, onResize is fired whenever the size of the window changes;
in Mozilla, it only fires when the mouse stops moving. It should, like IE, fire
whenever the size changes.

Reproducible: Always

Steps to Reproduce:
1. set an interval or set the onResize event
2. resize the window

Actual Results:  
the intervals and other javascript code weren't being fired and onResize was
only being called when the mouse stopped moving

Expected Results:  
executed the javascript code and fired onResize whenever the size of the window
changed

Comment 1

[Peter van der Woude [:Peter6]]

that would make the page reload constantly, nailing cpu use at 100%.
Not really desirable I'd guess.

The reload isn't needed if a page is properly designed / written

WONTFIX ?

Comment 2

[cdbarlow]

Why can IE continue running functions when the window is resized, even though
you say it is impossible? I simply need to have intervals running in the
background for something that I am writing (even while the window is being resized.)

You have no idea as to what I am writing and I don't see any reason why the page
would need to be reloaded constantly.

By the way, even "properly written" scripts may require a setInterval running in
the background; that's why setInterval even exists. Any real professional would
know that.

(In reply to comment #1)
> that would make the page reload constantly, nailing cpu use at 100%.
> Not really desirable I'd guess.
> 
> The reload isn't needed if a page is properly designed / written
> 
> WONTFIX ?

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.