Multiple error dialog stack order does not match focus order



Mail Window Front End
8 years ago
8 years ago


(Reporter: Dominic Benson, Unassigned)


Firefox Tracking Flags

(Not tracked)




8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100629 Mandriva Linux/ (2010.0) Firefox/3.6.6
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100624 Mandriva/3.0.5-0.1mdv2010.0 (2010.0) Thunderbird/3.0.5

If Thunderbird times out whilst trying to connect to a server more than once, without the error dialog being dismissed in between, the second dialog is hidden behind the first, but has forced-focus. In particular, this means that the dialog on top cannot be dismissed. It is necessary to <Enter> to dismiss the hidden dialog.

Reproducible: Always

Steps to Reproduce:
1. Prevent thunderbird from being able to reach a configured IMAP server
2. Open the inbox on that account
3. Wait for the activity message to indicate that thunderbird is connecting
4. Switch to another folder on the account

Actual Results:  
After a few minutes, two duplicate error dialogs are opened. One is hidden behind the other, and the one in the foreground cannot be clicked.

Expected Results:  
Either the second dialog should be on top, or both should be able to be dismissed independently.

Encountered under KDE 4.3.5

Creating with severity minor as there *is* an easy workaround, although it wouldn't necessarily be obvious to all users.

Comment 1

8 years ago
Missing step from steps to reproduce: after multiple dialogs appear, refocus on Thunderbird. 

This is what brings the first of the errors to the front. Also, it is possible to move/resize this message, but close/OK have no effect. The alternative workaround is to move the dialogs out of the way until finding one that can be dismissed.
This has been fixed in Thunderbird 3.1 by bug 123440. We're no longer producing modal dialogs, so you won't hit this issue.
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.