Closed
Bug 102056
Opened 23 years ago
Closed 20 years ago
Mozilla hangs when attempting to open an email from OTCJournalListServer
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: davidb, Assigned: sspitzer)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913 BuildID: 2001091303 Highlighting an OTCJournalListServer email instance results in an indefinite wait.... attempting to close the window results in Mozilla.exe not responding.. End Now... this has happened with several emails from this one source using Netscape 6.1 and now also in 0.9.4. Netscape 4.x seemed to be able to read similar emails from the same source without incident. (If its any consolation I have similar problems with Notes at work) Reproducible: Always Steps to Reproduce: . receive an email from OTCJournalListServer (how to achieve?) 2.click on email instance 3. Actual Results: Mozilla.exe hung Expected Results: Displayed the graphics of the message in the preview window
Comment 1•23 years ago
|
||
Reporter: Thanks for your email with that message. Can you try to disable Java in Edit/preferences/Advanced/Java and load this message ? Does it also hang mozilla ?
Comment 2•23 years ago
|
||
ok i can reproduce this bug with win2k build 20011013.. It seems that all message with Java will hang mozilla on win32 :-( See bug 103550 and bug 90802 but I don't want to dupe this bugs - Seth please help me :-) from email : i Matti, brilliant... it loads up fine..... btw... I also had and have javascript for mail and news disabled and yes it hung all mozilla related windows, mail and navigator rgds and ta
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•20 years ago
|
||
It has been 3 years since this bug has had any changes, I'm I can't find a way to test or reproduce this resolving invalid
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•