Closed
Bug 98886
Opened 24 years ago
Closed 24 years ago
Clicking on "New Message" or "Reply" causes Mozilla to freeze in latest nightly (2001-09-07)
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
People
(Reporter: Peter, Assigned: bugzilla)
Details
(Keywords: regression)
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3+) Gecko/20010907
Clicking on "New Message" or "Reply" causes Mozilla to freeze in latest nightly
(2001-09-07)
I can no longer send/reply with the current build, Yesterday, it still workrd.
Reporter | ||
Updated•24 years ago
|
Keywords: regression
Comment 1•24 years ago
|
||
I'm seeing the same problem in Windows 2000.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.3+) Gecko/20010907
Mail is useless for 60% of my work with this bug.
Comment 2•24 years ago
|
||
Some more description of the problem:
1) open email, read message (any message)
2) Hit reply - new message pops up but the original message is not automatically
quoted and no attribution automatically filled in. Can click into message body,
and can address messages (haven't tried sending though). Close message. You
can still open for reading new messages at this point, browser windows still works.
3) Hit reply on another message. All open windows hang with busy timer icon,
you have to close app to restore function.
Comment 3•24 years ago
|
||
i used 2001-09-12-05 build on win98. I was able to compose new message and send
as well as reply to a message and did not experience any freeze. Please try new
build.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 4•24 years ago
|
||
reopening since this is a dup
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 5•24 years ago
|
||
this is a dup of 97585
*** This bug has been marked as a duplicate of 97585 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•