Closed Bug 230181 Opened 22 years ago Closed 22 years ago

<embed> tag always shows up 'Click here to get the plug-in' link instead of loading the applet

Categories

(Core Graveyard :: Embedding: APIs, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 197813

People

(Reporter: peter.tolmachov, Assigned: adamlock)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031208 It is not possible to load applet with <embed> tag if 'type' attribute contains version that starts from 1.4 (e.g. type='application/x-java-applet;version=1.4.1') Reproducible: Always Steps to Reproduce: 1. Create applet java class e.g. com.applet.Select.java 2. Compile it into com.applet.Select.class file 3. Make a jar(e.g. SelectApplet.jar) that contain class file 4. Put resulted jar on some server that it can be accessed by some url(e.g. http://testhost/applets/SelectApplet.jar) 5. Create embed.html file that contains these html lines: <html> <head> </head> <body> <embed type="application/x-java-applet;version=1.4.1" code="com.applet.Select.class" codebase="http://testhost/applets/" ARCHIVE="SelectApplet.jar" NAME="selectapplet" WIDTH="100" HEIGHT="200" pluginspage="http://java.sun.com/products/plugin/index.html#download" > </embed> </body> 6. Open embed.htm using mozilla browser Actual Results: 'Click here to get the plug-in' link shows up Expected Results: Load an applet. I use Mac OS X version 10.2.4 (6132). Version of java plug-in is 1.4.1. If I change 'type' attribute in embed tag to version 1.3.1 (type='application/x-java-applet;version=1.3.1') than mozilla loads an applet.
Mozilla (and most other OS X browsers, except Safari) will only use Java Plugin 1.3.1, even if a later JRE is installed. *** This bug has been marked as a duplicate of 197813 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.