Closed
Bug 271735
Opened 20 years ago
Closed 20 years ago
tanzania-online.gov.uk - Firefox 1.0 crashes whilst loading the Tanzanian High Commission's website
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: hill, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
The Tanzanian High Commission's (admittedly, awful) website crashes Firefox but
loads OK in IE6. It's got lots of nasty animated gifs and a broken Java applet
on it (this is probably causing the problem, but surely shouldn't crash the browser)
Reproducible: Always
Steps to Reproduce:
1.visit the URL http://www.tanzania-online.gov.uk/
2.
3.
Actual Results:
Firefox crashed.
Expected Results:
Disabled the broken Java applet, and loaded the rest of the page, presumably.
Oooh. don't know that and can't find out without... crashing my browser.
The site wfm. Possible cause is the Java that's used.
Under TOOLS - OPTIONS - WEB FEATURES can you UNCHECK the "enable java" entry and
try again.
If the problem disappears, then your Java crashes Firefox and you should
reinstall your Java VM.
Can you report back on your findings?
Comment 2•20 years ago
|
||
Using FF1.0 + JRE 1.5, Java Console shows:
java.lang.NullPointerException
at button.init(C:\Windows\Desktop\Button Applet 1.1\button.java:186)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
got pm from reporter:
"Hello,
Yup that worked - thanks a lot. It was my Java, not Firefox. Sorry for the wild
goose chase.
Keep up the good work!
Christian "
resolving as wfm per reporter's feedback.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Summary: Firefox 1.0 crashes whilst loading the Tanzanian High Commission's website → tanzania-online.gov.uk - Firefox 1.0 crashes whilst loading the Tanzanian High Commission's website
You need to log in
before you can comment on or make changes to this bug.
Description
•