Closed Bug 776042 Opened 13 years ago Closed 5 years ago

on Send Mail Error, sending dialog remains forefront with ERROR dialog behind it

Categories

(Thunderbird :: Message Compose Window, defect)

14 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: educmale, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Build ID: 20120713134347 Steps to reproduce: On sending an email, a dialog pops up which declares it is sending the email. Sometimes, that send fails, either due to a disconnect, server time-out or other [unknown] cause. When that happens, that error forces another dialog to pop so declaring. However, the first dialog [sending] remains to the front, and the error dialog box [as it happens, wider Left/Right] is behind. In order to dismiss the error DLG, I have to select it first, and the acknowledge the error, at which point both DLGs disappear Expected results: When a SEND mail request results in a Sending DLG box, and an error occurs which brings up an ERR DLG, the ERR dialog should be foremost. Whether or not the original SENDing DLG should remain, I haven't thought deeply on, but at the least, it should be behind the ERR DLG This may be in the same coding area as might be encountered with Bug 120278, and might both be cured in the same swoop.
Component: General → Message Compose Window
See Also: → 1072628

John, does this still reproduce?

Flags: needinfo?(educmale)

Resolved by subsequent versions, it seems. In contrast, I have the sense that the related bug #1072628 does happen from time to time, and can't fairly say it is (or isn't) resolved by the current version.

Flags: needinfo?(educmale)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID

Thanks John. The feedback is much appreciated.

And thanks for closing your own bug. Nit - we use WORKSFORME when the problem goes away but we don't know why

Resolution: INVALID → WORKSFORME
You need to log in before you can comment on or make changes to this bug.