20040706 trunk STEPS TO REPRODUCE: 1. Open a compose window. 2. Close it. RESULT: Thunderbird prompts you to save the message. EXPECTED: Just close the window (nothing has been typed yet). This is a regression.

This happens on Linux also. Setting OS to All.

Jerry Baker, do you still see this bug under Windows? I don't. Reporter of bug 262772 claims problem still exists under Linux. I think one should be duped, and the other should probably have its OS reset to Linux.

I do not see it using a recent trunk build on WinXP.

It's back, and with a twist. If you reply to a message and close the window without typing anything, it just goes away as aexpected. If you open a new composition and close it, you get prompted.

Bug 321783 reports what might be key: the first compose opened after restart always prompts, but subsequent ones don't.

I can open and close compose windows a hundred times and it asks 100 times. Perhaps I am misunderstanding?

No, you don't misunderstand; but you're not seeing the same symptom I am, probably because you've got a different configuration.

Ok. I just didn't want the owner to think this only happens once after you start Thunderbird.

(In reply to comment #5) > Bug 321783 reports what might be key: the first compose opened after restart > always prompts, but subsequent ones don't. actually, not quite. slightly more complex than above because switching accounts also resets and tickles the behavior. testcase, windows: 1 select imap account 1 2 compose 3 close 4 -> TB prompts 5 repeat 1-3 6 -> no prompt 7 select imap account 2 8 repeat 2-6 with account 2 - same behavior 9 select local folder 10 repeat 2-6 with local - same behavior repeat with account 1 if you like reproducible: always how do bug 262772 and bug 321783 differ, beyond that this did apparently never regressed on linux? i.e. why are none of them duped? is there a time range on the regression window?

I think I've noticed this before in 2.0.0.12, though if I close the Empty Compose window immediately after opening, I don't get the dialog. I do get the dialog after a couple seconds wait though, occasionally.

I'm duping this to bug 262772. Hard to tell how that and bug 321783 really relates.