248704 - Loop breaks in Firefox when moving the mouse and clicking randomly

Status: RESOLVED EXPIRED

(Core :: DOM: Core & HTML, defect)

Description

[XFox]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040623
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040623

The puzzle game at http://xfox.digibase.ca/games/slide/tornado/ has problems
with the scramble button. In Firefox, when the user scrambles, it updates the
status bar with a percentage and moves the pieces one at a time (which the user
can see). If you move the mouse around or click randomly while the script is
processing, it will break.

Reproducible: Always
Steps to Reproduce:
1. In Firefox 0.9, Go to http://xfox.digibase.ca/games/slide/tornado/
2. Hit the scramble button and don't move the mouse.
3. Click around or move the mouse and the script will break. If not, scramble
again and it will.

Actual Results:  
The function breaks before the for loop finishes

Expected Results:  
The function should go uninterupted. Script should be handled the same way as
Mozilla handles it.

This is a FireFox only problem. It takes 40 seconds to complete scrambling in
Firefox. However, it takes 3 seconds in Mozilla. For some reason, Mozilla skips
the step of displaying the percentage in the status bar and updating the screen
piece by piece. I really don't know why Mozilla skips this step when Firefox
doesn't, but speed is everything. Many users are thinking that their browser is
hanging.

Comment 1

[Hermann Schwab]

wfm Mozilla 1.7
needs 18 seconds to scramble, I see the tiles moving in the image, and a
percentage display in the status bar.

partly wfm Mozilla 1.8a
needs 12 seconds to scramble, seems that I only see the first change of the
image, and the last one, and no display in the status bar

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040624
tested on the same computer, Celeron 333, 96 MB RAM, 800x600, 8 MB SiS6326
graficscard

Comment 2

[Boris Zbarsky [:bzbarsky]]

Setting status has known issues.

That said, a clear description of what "the scrip will break" means would be
very helpful in testing this bug...

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.