Closed
Bug 199884
Opened 21 years ago
Closed 21 years ago
Printing previously-saved mail message makes Mozilla freeze.
Categories
(MailNews Core :: Printing, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: michael.graubart7, Assigned: dcone)
Details
Attachments
(1 file)
2.43 KB,
message/rfc822
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.3b) Gecko/20030115 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.3b) Gecko/20030115 I saved a mail message to my desktop. Subsequently I tried to print it, but every time Mozilla froze up. Reproducible: Always Steps to Reproduce: 1. Save a message from the mail window as xxx.eml. 2. Close Mozilla. 3. Double-click on the saved message to start Mozilla and open the message. 4. Choose 'Print'. Actual Results: Mozilla froze up. Expected Results: It should have allowed the message to be printed. Mac G3 (old beige), OS 9.2.2. Modern theme. I am using Build 2003011508 because later builds have not been made available for OS 9.x. I shall attach the message that caused the problem.
Reporter | ||
Comment 1•21 years ago
|
||
Reporter | ||
Comment 2•21 years ago
|
||
I have now discovered that once again – YET once again! – Mozilla had become corrupted, and froze up even when I tried to print currently-displayed messages from my inbox. I have once again had to uninstall Mozilla and re-install it from scratch; I can now print OK. I have no idea what could have damaged Mozilla. This instability, which manifests itself in various ways (e.g. also in connection with the bookmarks file) is very worrying.
Unfortuanly support for mac classic is dead :-( -> WONTFIX. If this also occurs on OSX, please reopen and change the OS field. However there does exist an unofficial 1.3 where this might be fixed, see <http://www.google.com/groups?selm=3E7649F2.7060807%40yahoo.com>
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•