nsIMsgWindow Interface Reference

import "nsIMsgWindow.idl";

Inheritance diagram for nsIMsgWindow:

Inheritance graph
[legend]
Collaboration diagram for nsIMsgWindow:

Collaboration graph
[legend]

List of all members.

Public Member Functions

void displayHTMLInMessagePane (in AString title, in AString body, in boolean clearMsgHdr)
void StopUrls ()
void closeWindow ()
 when the msg window is being unloaded from the content window, we can use this notification to force a flush on anything the msg window hangs on too.

Public Attributes

attribute nsIMsgStatusFeedback statusFeedback
attribute nsIMsgWindowCommands windowCommands
attribute nsIMsgHeaderSink msgHeaderSink
attribute nsITransactionManager transactionManager
attribute nsIMsgFolder openFolder
attribute nsIDocShell rootDocShell
readonly attribute nsIPrompt promptDialog
attribute ACString mailCharacterSet
attribute boolean charsetOverride
 Remember the message's charaset was overridden, so it can be inherited (e.g for quoting).
attribute boolean stopped
 Has a running url been stopped? If you care about checking this flag, you need to clear it before you start your operation since there's no convenient place to clear it.
attribute nsIDOMWindowInternal domWindow


Member Function Documentation

void nsIMsgWindow::displayHTMLInMessagePane ( in AString  title,
in AString  body,
in boolean  clearMsgHdr 
)

void nsIMsgWindow::StopUrls (  ) 

void nsIMsgWindow::closeWindow (  ) 

when the msg window is being unloaded from the content window, we can use this notification to force a flush on anything the msg window hangs on too.

For some reason xpconnect is still hanging onto the msg window even though all of our objects have let go of it this forces a release...


Member Data Documentation

attribute nsITransactionManager nsIMsgWindow::transactionManager

attribute ACString nsIMsgWindow::mailCharacterSet

Remember the message's charaset was overridden, so it can be inherited (e.g for quoting).

Has a running url been stopped? If you care about checking this flag, you need to clear it before you start your operation since there's no convenient place to clear it.


The documentation for this interface was generated from the following file:

Generated Mozilla by doxygen 1.5.6