With a current CVS trunk build (or a official nightly, here 2005-02-25-03) you can't reply to a mail or compose a new mail. When you click Reply/Compose, it opens the Compose window, but then you only get a busy mouse cursor over and over again (the mouse cursor changes every few ms from normal to busy and back). In the JS Console this error appears: Error: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgCompose.initEditor]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: ComposeStartup :: line 1351" data: no] Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js Line: 1351 This blocks smoketest M.1, M.2, M.4 and probably M.12, too.

Bonsai link (regressed between 2005-02-24-05 and 2005-02-25-03): http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-02-24+04%3A00%3A00&maxdate=2005-02-25+04%3A00%3A00&cvsroot=%2Fcvsroot This also broke Composer.

Sorry, attached the wrong patch last time.

I got r+sr=bz on #developers

This may not be a problem with mailnews etc, but it is for some extensions that use the editor. We end up re-initializing the editor, which ends up, in the non-midas case, re-adding the editor as a web progress listener. That fails (since it's already a listener) in nsEditingSession::PrepareForEditing(), which ends up throwing an error, all the way back to the caller.

Comment on attachment 175558 [details] [diff] [review] Make re-initializing the editor from code other than midas work again. r=brade

Comment on attachment 175558 [details] [diff] [review] Make re-initializing the editor from code other than midas work again. sr=bzbarsky

*** Bug 283705 has been marked as a duplicate of this bug. ***

*** Bug 283677 has been marked as a duplicate of this bug. ***

*** Bug 283821 has been marked as a duplicate of this bug. ***