User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 When forwarding a mail message with an IMAP account, Thunderbird crashes when I hit ctrl+enter to send before navigating away from the "To:" field. Check spelling before sending option must be switched on. Reproducible: Always Steps to Reproduce: 1. Test using an IMAP account and make sure "Check spelling before sending" option is checked. 2. Click to forward a message from your mailbox. 3. Enter in an address in the "To:" field, and do not navigate away from the "To:" field. Hit Ctrl+enter to send. 4. Crash. Actual Results: Crash. Expected Results: Send the message. See attached screenshot.
Also happens with Windows XP.
I was also able to reproduce this bug. In addition to having spell checking enabled, however, the following conditions also had to be met for it to crash on my machine: 1. Under 'Composition' settings, I have to have "Forward Messages: Inline" selected instead of "Forward Messages: As Attachment". 2. Also under Compisition settings, I have to have "Confirm when using keyboard shortcut" UNCHECKED. If the above conditions are met in addition to what Kevin described, the described effect occurs for me. I am using release 0.4 (20031205) on Windows XP SP1.
thanks for the detailed steps.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Thunderbird0.5
Hmm, following those steps, things seem to work here on the latest 0.5 alphas.
Downloaded and tested with build 0.5a (20040120). I discovered that there must be a misspelled word in the forwarded message to trigger the crash.
moving these bugs to 0.6
Target Milestone: Thunderbird0.5 → Thunderbird0.6
Kevin, do you still see this crash in a recent nightly? http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2004-03-12-trunk I can't seem to trigger it.
Nope, I can't trigger the crash anymore either with the new build.
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
*** Bug 237715 has been marked as a duplicate of this bug. ***
I'm using TB 0.9, still having this problem.
You need to log in before you can comment on or make changes to this bug.