220908 - No way to not have nsIMsgCompose.sendMsg close window if window specified

Status: RESOLVED EXPIRED

(MailNews Core :: Composition, defect)

Description

[Erwin Wessels]

User-Agent:       Mozilla/4.8 [en] (Windows NT 5.1; U)
Build Identifier: Mozilla Thunderbird 0.2 (20030901)

When using nsIMsgCompose.SendMsg from an extension, it is not possible to not
have it close the specified window (as specified in 2nd parameter of
Initialize). This renders this method (the only way to send an email from an
extension) nigh useless when you want to specify an editor (otherwise this
problem can be circumvented by not specifying a window at all).

Reproducible: Always

Steps to Reproduce:
1. In a JS extension do a 
Components.classes["@mozilla.org/messengercompose/compose;1"].createInstance(Components.interfaces.nsIMsgCompose);
2. Call this object's Initialize method with a handle to a window and an
instance of nsIMsgComposeParams.
3. Call this object's InitEditor method with a handle an editor object on the
window, and a handle to the window.
4. Call this object's sendMsg method with parameters that tickle your fancy (as
long as a message gets send, that is).
Actual Results:  
The window specified is closed (after the email is sent.) There is no (clear?)
way to prevent this.

Expected Results:  
Allow for an option to have the window stay open.

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.