210793 - Compose window gets lost behind other windows when send fails

Status: RESOLVED EXPIRED

(MailNews Core :: Composition, defect)

Description

[K.C. Baltz]

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

When I try to send an encrypted email to someone for whom I don't have a cert, I
receive an error dialog to that effect.  That's expected.  However, some of the
time, when I click ok on this dialog to dismiss it, the compose window is lost
behind the main email window, as if it had been closed.  However, it's still
open and can be found using alt-tab.  

I notice a difference between when this bug occurs and when it does not:

When it does occur, the Sending Message dialog appears in addition to the Send
Message Error dialog.  It lists the Status as "Creating mail message".  If this
dialog is present, then the bug will occur (the compose window will be lost
behind the main window).  I'll attempt to attach a picture of this to the bug
report.

Reproducible: Sometimes

Steps to Reproduce:
1. Compose a new message.  Set it to be encrypted, but make sure the addressee
is someone for whom you do not have a signed certificate.
2. Click Send.  If the bug is going to occur, you must receive two dialogs, the
Sending Message dialog and the Send Message Error dialog.  Not sure how to force
this to happen; it seems to be a race condition.
3. Click OK on the Send Message Error dialog to dismiss it. 
Actual Results:  
If both dialogs appeared, then the compose window will be "lost" behind whatever
other window you have on the screen. (E.g. if the compose window was on top of
the  main inbox window, it will now be lost behind it.)

Expected Results:  
Compose should have remained the top, focused window.

Comment 1

[K.C. Baltz]

Attachment: Picture of the two dialogs that appear when the bug occurs

Comment 2

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

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