I've also tried that and received the exact same error message. Why is an nsIMsgWindow even needed? Last I had seen (in this newsgroup anyway), a msgWindow was needed for updating status for the gui and could have null safely passed in instead of an actual window. Of course it isn't working for me, so...
What are the ramifications of setting the DOM window though? If I set the DOM window I believe it blocks certain javascript functionality from happening in the current window. For what I need to be able to do I can't block js functionality since other javascript will be running in that window at the same time. Is there any other way to go about getting message info besides getting an nsIMsgDatabase (by message info I mean header information for the most part - to, from, date, etc.). Dan Neil wrote: > > Which won't work, so pass in an nsIMsgWindow instead. > > msgWindow = > Components.classes[@mozilla.org/messenger/msgwindow;1].createInstance(); > msgWindow = msgWindow.QueryInterface(Components.interfaces.nsIMsgWindow); > > The question is, do you need to call msgWindow.SetDOMWindow before you > can use it? >
