Closed Bug 60343 Opened 25 years ago Closed 25 years ago

After installing the netscape java plugin, applets don't display properly

Categories

(Core Graveyard :: Java: OJI, defect, P3)

x86
Linux

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: sheldon, Assigned: serhunt)

References

()

Details

1) Install mozilla M18 Mozilla/5.0 (X11; U; Linux 2.2.17 i686; en-US; m18) 20001010 2) Go to the applet verification page 3) You are asked to install the Netscape java plugin 4) Allow this to be installed 5) Restart mozilla, return to the verification page 6) No applet is displayed in the mail browser window. A small dislog is opened, but it's too small to see what it displays, and it can't be enlarged. 7) Other applet pages that work under netscape show similar problems. I can supply other examples upon request.
Reporter, M18 is seen as "old" in the Mozilla world, and the Java plugin/API has been changed since then. Please consider downloading the latest build of Mozilla (http://ftp.mozilla.org/pub/mozilla/nightly then chose the latest MTrunk dir). If you still see this behaviour, please comment further. Thank you, Fabian. (Over to OJI)
Component: Plug-ins → OJI
I installed a recent build from 2 nights ago Mozilla/5.0 (X11; U; Linux 2.2.17 i686; en-US; m18) Gecko/20001116 This fixes the Verification/Applets page: the clock now appears. An example of a page that still doesn't work (and works under netscape) is http://www3.fide.com/ist/cup.cgi?date=20001102&champ=men&pare=005_HUN_CZE&pgn=2
The fide.com applet works for me with mozilla linux trunk 2000111608 and jre 1.3.0_01. What jre do you have (the version number is in the java console, which is under the tools submenu of the Tasks menu)? One thing. It took about 10 seconds for the applet to start up for me. so you may want to give it a bit of time.....
worksforme on 20001116 trunk build
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Verified.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.