Closed Bug 315539 Opened 20 years ago Closed 20 years ago

Java Applet doesn't show in Camino.

Categories

(Camino Graveyard :: Plug-ins, defect)

Product:
Camino Graveyard
Component:
Plug-ins
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: klassej, Assigned: mikepinkerton)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051107 Camino/1.0+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051107 Camino/1.0+ The Live support Applet that is launched does not work in Camino, the page is blank. Works fine in Safari so it should be related to Camino and not the JVM. http://www.java.com/en/download/help/testvm.xml Reports: Vendor: Apple Computer Version: 1.4.2_09 OS: MacOSX Version: 10.4.3 Reproducible: Always Steps to Reproduce: 1. Open the URL 2. Fill out something in the required fields and press submit 3. Applet loads but does not show anything Actual Results: Blank page Expected Results: Live Support Applet should show, compare to Safari
WFM 2005110708 (v1.0b1), with JEP 0.9.5+b (released today). The certificate for the applet was expired, but I accepted it anyway and had a nice chat with a friendly support rep explaining why I filled in bogus values, etc. (I think the cancel button is part of the applet, so I could have cancelled before the chat, but I was just being thorough....) Is this broken on the trunk only, perhaps?
It reproduced it only once. The following pages were displayed with another Tab at this time. The applet was not displayed as for this page either. http://fukuoka.cool.ne.jp/fullhouse/labo/labo9.html The following messages were displayed in the console log at this time. 2005-11-09 21:41:02.179 Camino[17187] JEP creating applet BulletinBoard (http:// fukuoka.cool.ne.jp/fullhouse/labo/) Tried to create the VM in the Java Applet.plugin. We detected that one already was created for this browser. Using existing VM. **Warning** this VM MAY not have the expected Java Runtime Parameters. Java Embedding: requires a Java 1.3.1 VM CreateJavaApplet: err = -1 Mac OS X 10.3.9 trunk build 2005110708 (v1.0+)
crot0's applet displays for me, too: 2005110708 (v1.0b1), with JEP 0.9.5+b This is either trunk-only or JRP 0.9.5+a, which is the JEP version on the trunk in those builds. klassej@gmail.com, can you check again with today's trunk nightly, which should have JEP 0.9.5+b (and do you get any error messages in the console.log when you try to load the Live Support applet--or any other applets)? Steven, does that console error correspond to a known problem with JEP 0.9.5+a?
> Steven, does that console error correspond to a known problem with JEP > 0.9.5+a? Nope. I've never seen (or heard of) anything like this before. I wonder if this problem is related to bug 313700. Please check to see if about:plugins lists the Java Embedding Plugin more than once, or if it lists the wrong version (not the one that's bundled with your Camino distro). If so, try renaming your pluginreg.dat file (in ~/Library/Application Support/Camino). (Also upgrade to JEP 0.9.5+b. The main bug it fixes only effects Carbon browsers. But the other fixes also effect Camino, and are worth having.)
(In reply to comment #3) > crot0's applet displays for me, too: 2005110708 (v1.0b1), with JEP 0.9.5+b > > This is either trunk-only or JRP 0.9.5+a, which is the JEP version on the trunk > in those builds. > > klassej@gmail.com, can you check again with today's trunk nightly, which should > have JEP 0.9.5+b (and do you get any error messages in the console.log when you > try to load the Live Support applet--or any other applets)? > > Steven, does that console error correspond to a known problem with JEP 0.9.5+a? > Updated to: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051108 Camino/1.0b1 It now works fine, the content of the Applet shows.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
WFM...
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
I tested with crot0's URL (http://fukuoka.cool.ne.jp/fullhouse/labo/labo9.html) on OS X 10.3.9 and 10.4.3, using JEP 0.9.5, 0.9.5+a and 0.9.5+b, with Camino 0.8.4, Firefox 1.0.7 and a couple of fairly recent Camino nightlies (2005-10-25-04-1.0 and 2005-10-25-08). I didn't see any of the problems crot0 reports, but I did sometimes see a doubling of the applet in the 2005-10-25-08 nightly (on the trunk): xThe applet appeared both at the top of the page and the bottom, the bottom copy moved with the bottom of the window when I resized it, and it appeared in more than one tab (when I switched tabs or created a new one). It was fairly easy to trigger this by clicking on the applet (which took you to another page), and then switching back and forth between these two pages using the forward and back buttons. This must be a problem with the Camino trunk nightly. Just now I've tested the 2005-11-09-08 (trunk) and 200-11-08-1.0 (branch) nightlies, each with all of JEP 0.9.5, 0.9.5+a and 0.9.5+b on OS X 10.3.9. I still see the same thing -- a frequent doubling of the applet with the trunk build, and no problems at all with the branch build.
More on the wierd applet doubling: When the applet appears at both the top and the bottom of the page, it really is being loaded twice -- in both the Java console and the system console the JEP shows two of the following message: Wed Nov 09 21:17:23 CST 2005 JEP creating applet BulletinBoard (http://fukuoka.cool.ne.jp/fullhouse/labo/) But there's only one APPLET tag in the page. I still think this has to be a bug in recent Camino trunk nightlies ... but I've no idea what the bug might be.
So the non-display is fixed now on the trunk? Someone with a trunk build should open a new bug on the "doubling" on the trunk, though....
> Someone with a trunk build should open a new bug on the "doubling" on the > trunk, though.... I'll do that once I've had a chance to look into it further. Probably sometime in the next few weeks.
You need to log in before you can comment on or make changes to this bug.