Closed Bug 627883 Opened 15 years ago Closed 15 years ago

Not recognizing application/x-java-applet;version=1.6

Categories

(Core Graveyard :: Plug-ins, defect)

x86_64
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 630285

People

(Reporter: Gnonthgol, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b9) Gecko/20100101 Firefox/4.0b9 Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b9) Gecko/20100101 Firefox/4.0b9 When I enter a web site that is jusing a java plugin with type="application/x-java-applet;version=1.6" firefox prompts me to install java. about:plugins reports that the java plugin handles boath application/x-java-applet;jpi-version=1.6.0_22 and application/x-java-applet;version=1.5 This is not a problem with safari or firefox 3.5 whitch have the entry for application/x-java-applet;version=1.6 in about:plugins Reproducible: Always Steps to Reproduce: 1. Create a html page including <EMBED type="application/x-java-applet;version=1.6" ...> </EMBED> 2. Browse to that html page 3. Actual Results: Firefox complains off missing plugin for java Expected Results: Starts the java plugin
Component: Extension Compatibility → Plug-ins
Product: Firefox → Core
QA Contact: extension.compatibility → plugins
Version: unspecified → Trunk
I am experiencing similar problem with SeaMonkey 2.0.11. Have updated Java to Version 6 Update 23 (build 1.6.0_23-b05), SeaMonkey won't work on page requiring Java (says to install Java, which is already listed in plug-ins, and is active). Same page works fine in MS IE 8.0 and Google Chrome.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
The problem I described in my comment above was resolved when I uninstalled Java, carefully hunted for and deleted old versions of the Java plug in from past installs, and reinstalled the current Java. Then pages with Java on them loaded fine, so my problem was not a bug. Sorry to muddy the waters.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.