471506 - Minimizing main window after clicking a link that results in a file download dialog causes Firefox to stop responding to input

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Bear]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729)

If Firefox is minimized after clicking on a link but before the save/open dialog appears, the program stops responding because the save/open dialog has the focus but it is not visible.

The program does not respond to any hotkeys including alt+F4.

Additionally, user is unable to restore the window or use the context menu on the task bar to close the window.

The only way to gain control is to kill Firefox using the task manager and restart it.

Reproducible: Always

Steps to Reproduce:
1. Click a link that takes some time to open.
2. Minimize Firefox.
3. Firefox taskbar button is visible but the program does not respond to input.
Actual Results:  
Firefox stops accepting input from the user.

Expected Results:  
Firefox should respond to input from the user.

Comment 1

[Tyler Downer [He/Him]]

This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days.

Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to  RESOLVED, WORKSFORME.

Comment 2

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.