267105 - Dialog boxes are not processed when input is given to them but wait for a cleanup thread (or something)

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[TJ Wilson]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

When a dialog box ('Confirm', 'About', etc.) is given input (to an OK button 
for example), the input is not processed until a cleanup thread (or some other 
such process) is given enough priority to destroy it.

This can lead to the browser continuing unwanted behavior until the system gets 
around to giving the thread some resources.

Reproducible: Always
Steps to Reproduce:
1. Use a slow computer (like a P-Pro 233 for instance) bogged down with lots of 
stuff running.
2. Load webpages that requires POST information across several tabs (10 should 
be very sufficient).
3. Click the first tab
4. Refresh the tab
5. Click OK (or press Enter) on the 'Confirm' dialog box.
6. Repeat steps 3 and 5 for each tab.

Actual Results:  
The processing of each 'Confirm' dialog takes longer and longer as system 
resources are given to the refreshing tabs. Eventualy it can take upwards of 10 
to 20 seconds to resolve a confirmation box.

Compounding the problem is the behavior where the Confirm dialog locks input to 
the entire browser until it is resolved and destroyed, making the browser 
completely non-responsive to user input attempts.

Expected Results:  
The confirmation box should have been resolved and destroyed at the time the 
input was given to it.

Comment 1

[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 2

[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.