Last Comment Bug 57689 - Webclient can't view applets.
: Webclient can't view applets.
Status: ASSIGNED
:
Product: Core Graveyard
Classification: Graveyard
Component: Java APIs to WebShell (show other bugs)
: Trunk
: x86 Windows NT
: P3 major with 2 votes (vote)
: ---
Assigned To: edburns
: Alexei V. Mokeev
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-23 11:18 PDT by edburns
Modified: 2012-04-09 22:27 PDT (History)
1 user (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description edburns 2000-10-23 11:18:55 PDT
Can't view applets with webclient.
Comment 1 edburns 2000-10-23 11:19:51 PDT
a
Comment 2 Boris Zbarsky [:bz] (still a bit busy) 2000-10-23 13:11:10 PDT
duplicate of bug 57046?
Comment 3 edburns 2000-11-08 16:45:16 PST
Applets work on Solaris.
Comment 4 geetha.vaidyanaathan 2000-11-17 13:55:27 PST
Have tested Webclient with SVR4 pkg from SUN and confirm that  I am able to load
applets within Webclient on Solaris.
Comment 5 Alexei V. Mokeev 2000-12-05 00:29:35 PST
Applets works under Sparc Solaris 2.7 with FCS-candidate(from 11/30/2000)
Comment 6 Alexei V. Mokeev 2001-05-03 04:16:32 PDT
Changing QA contact
Comment 7 Vladimir Strigun 2001-05-23 07:57:34 PDT
I reproduce this bug on NT with latest Webclient.
Comment 8 Vladimir Strigun 2001-05-23 07:58:48 PDT
Webclient can view applets on Linux SMP.

Comment 9 edburns 2001-06-13 12:31:06 PDT
Right, this works on Linux because the JVM is in a separate process.  THere are 
some broken assumptions made by the win32 java plugin that cause applets not to 
work there.  This bug depends on the Sun JDK release schedule.  It probably 
won't be fixed until JDK 1.5.  Sometime in 2002.

Ed
Comment 10 Vedu 2002-02-11 22:05:00 PST
This seems to be fixed in 1.3.1 atleast. 
I was having the same issue after installation(It reports the error when the 
plug-in was installed in a different directory other than the default one.)
When I changed the JRE path in Advanced Setting in Control Panel, it started 
working fine.
Comment 11 James Rose 2003-05-15 11:08:43 PDT
I reproduce this bug on MacOS X 10.1 with Mozilla 1.4b.

Note You need to log in before you can comment on or make changes to this bug.