Comments on: A fix for Java applets not loading in Firefox

By: Ben

Ben — Thu, 10 Sep 2009 02:17:39 +0000

You’re right about the documentation – nothin’. I upgraded to Ultimate 64 bit and this problem kicked in. Fix works great, thanks!

By: chris

chris — Tue, 01 Sep 2009 19:21:10 +0000

Great fix, this issue is still very much present in the latest version Firefox on Windows 7 RC 64bit

It had been driving me mad!

Thanks

By: Clive

Clive — Thu, 13 Aug 2009 17:31:29 +0000

Superb!! That solved that problem on my Win 7 RC 64-bit!! Thanks!!

By: Nowonmai

Nowonmai — Mon, 06 Jul 2009 06:07:59 +0000

I tried all this, but the only Java applets on certain sites will load up is if I either use Firefox in full safe mode, or use IETab. Yes, I have the np*.dlls in the plugin directory, yes, the sites are whitelisted for both NoScript and AdBlock, but still won’t launch the applets.

By: Bonnie

Bonnie — Tue, 09 Jun 2009 20:44:01 +0000

Woo, it works! This is very much appreciated. :)

By: Alex

Alex — Sun, 07 Jun 2009 12:58:05 +0000

Matthew!! Thank you so much for this fix, it was driving me nuts to have to use IE for java – keep up the good work

By: Ireneusz

Ireneusz — Wed, 03 Jun 2009 06:19:06 +0000

Hi.

Tanks for a this FIX. A have this issue and you helped me ! Tanks !

By: Matthew DeCarlo

Matthew DeCarlo — Thu, 21 May 2009 16:20:42 +0000

Right – that two year old bug is the only faint hint of an official recognition that I was able find. It may or may not be 100% related to the current issues people like you and I have been experiencing.

And yes, periodically you probably *will* have to recopy and paste the .dll’s.

By: coldFuSion

coldFuSion — Thu, 21 May 2009 15:40:50 +0000

The bug you link to is actually quite old (12-MAR-2007)

According to the bug one of the causes is blamed on Mozilla’s registry entries being different from one version of its browser to another.

- BrowserJavaVersion issue root cause:
The problem with BrowserJavaVersion key is not a regression in our code, rather it is caused by changes in Mozilla’s treatments for its registries which we depended on:

So who is to blame? Mozilla for frequently changing the registry structure of their browser or Sun for failing to keep their code up to date to properly detect Firefox?

Ironically this is mentioned twice in the bug:
please NEVER do any dll copying to workaround the problem.

Presumably because the next Java update will likely fail to install/update the plugin requiring that it be manually copied again.

Your article has java not working at all so IMHO at least there IS a workaround to get it working until someone decides how to fix this bug once and for all

By: Matthew DeCarlo

Matthew DeCarlo — Thu, 21 May 2009 14:53:08 +0000

You’re welcome. Hopefully it solves a lot of headaches.