regression on 2008-02-20 build, 02-19 build is OK according to stephend. /mail/mailnews checkins Bug 81091: Go|Next|Starred Go|Previous|Starred (was Flagged) message shouldn't be grayed out (standalone message window) r=philringnalda, sr=neil Bug 418282 Drop redundant mentions of nsIAuthPrompt in mailnews r/sr=Neil Mark's bug 410149 checkin is also nearby

Maybe bug 412920?

(In reply to comment #1) > Maybe bug 412920? seems likely cc: Peterv

[12:39] <cpearce> stephend: hmm that shouldn't happen... that bug is unclear, what does "empty message body" mean? shouldn't there be nothing in a new mail body anyway? or is it missing the signature? [12:40] <stephend> cpearce: it means if you type in the body, and send, that the recipient doesn't see any content in the message body ##### [12:40] <stephend> does the |editor| instance get destroyed on send, I wonder? [12:41] <stephend> and its nodes torn down? I think editor gets destroyed when a new document is loaded in the same docshell, when a page is hidden before an unload, or when all editable nodes in its doc are made non-editable or unbound. Its editable nodes get cleaned up in the next gc though. This could be caused 412920, I'm checking now. If it is, the send-message code probably needs to get an owning reference to the document it's sending before it starts disposing of stuff.

If I send (from HTML compose) text only, I get a blank; HTML only, I get the message; HTML + text I get the HTML part, and a blank text part (and remember, if you send HTML mail that can be losslessly converted to text, we do, so you wouldn't have to realize that you're sending text from HTML compose). Whether I'm right about bug 417384 being the cause, I think this and bug 418727 are the same thing, failure to serialize plaintext.

Ugh, this is regression from bug 417384.

Oops, I was going to put that message to Bug 418727

Verified dup