Closed Bug 351057 Opened 18 years ago Closed 18 years ago

Reply not working in build 20060901 (Editor Instance is DOA)

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED
Thunderbird 3

People

(Reporter: klubinsky, Assigned: mscott)

References

Details

(Keywords: regression, smoketest)

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Avant Browser; Avant Browser; .NET CLR 2.0.50727) Build Identifier: version 3 alpha 1 (20060901) When clicking reply, the reply to: address is not populated, the body of the e-mail is not populated with the original message, and nothing can be entered in the body of the message. Reproducible: Always
I saw this bug listed in the MZ forums. Thanks for filing it and linking the bug # in the forum post Kevin.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Also noted that when I type an e-mail address into the TO field, if I close/cancel the message, and then try to reply/forward any other message in the inbox that the address I entered in the original reply attempt remains populated in the TO field.
the HTML Editor instance is uneditable. Reply text doesn't get inserted and with new message compose you can't type anything into the editor instance.
Severity: major → blocker
Summary: Reply not working in build 20060901 → Reply not working in build 20060901 (Editor Instance is DOA)
Target Milestone: --- → Thunderbird 3
I backed out Bug 287707 and mail compose started working again.
Blocks: 287707
I've backed out the patch for bug 287707, so this should be fixed now in tomorrow's build. I clearly need to test Thunderbird also, before screwing around with designMode.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Thanks for the quick response Martijn!
*** Bug 351052 has been marked as a duplicate of this bug. ***
This is working fine again in a 2006-09-01-18 build of SeaMonkey trunk under Windows XP.
Status: RESOLVED → VERIFIED
*** Bug 351058 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.