Latest Firefox Dev 64 bit @ Win8 does not detect Java 8u51 64 bit
Java 8u45 worked OK in Firefox Dev 64 bit. This week I uninstalled Java 8u45 and installed new Java 8u51 into `C:\Java`. Now the plugin is not listed in Plugins at about:addons.
தீர்வு தேர்ந்தெடுக்கப்பட்டது
at the moment it's a hardcoded whitelist in firefox so i don't think it possible to work around that. maybe there will be some form of user controlled whitelist at a later stage, but the strategy that was put forward for win64 around plugins is a "clean slate approach": https://wiki.mozilla.org/Firefox/win64/meetingarchive#Clean_Slate_Approach
Read this answer in context 👍 2All Replies (14)
hi iki, that's to be expected - windows 64bit versions come with limited plugin support at the moment (only flash is whitelisted). if you depend on other npapi plugins please continue to use regular 32bit builds.
hi philipp, thanks for fast reply.
I can switch to 32 bit, but would prefer to stay with 64 bit. Is there a way to whitelist the Java plugin? I'm asking, because it worked perfectly with our Java app before last Firefox Dev update.
தீர்வு தேர்ந்தெடுக்கப்பட்டது
at the moment it's a hardcoded whitelist in firefox so i don't think it possible to work around that. maybe there will be some form of user controlled whitelist at a later stage, but the strategy that was put forward for win64 around plugins is a "clean slate approach": https://wiki.mozilla.org/Firefox/win64/meetingarchive#Clean_Slate_Approach
OK, that makes sense
... otoh Java plugin could be evaluated too, because NPAPI is now definitely disabled in Chrome>=42, and Firefox is the first choice for Java apps atm.
Weelll folks that means your only choice for Java at this point is Window Internet Explorer which worked today with Java 8 u66.
I think it is not-acceptable to not retain support for Java in the 64-bit frame while supporting it in the 32-bit version.
Another important point, is to take care of users, not like Chrome and provide a transition from the now plug-in container scheme to the new plug-in container scheme(s) -- Plural because these things are always improving. Be agile, ... be prepared.
philipp said
at the moment it's a hardcoded whitelist in firefox ...
I am praying for Java support in 64bit version of Firefox for Windows. There is no other acceptable web browser for me.
If you need Java install the 32-bit version of Firefox to use when you want Java. It is possible to have both the 32-bit and 64-bit versions of Firefox installed.
the-edmeister said
If you need Java install the 32-bit version of Firefox to use when you want Java. It is possible to have both the 32-bit and 64-bit versions of Firefox installed.
Why should I have installed two versions?! I installed 64bit version just to utilize 16 GB of memory so I will not install 32bit version. Is 64bit Java support planned or not?
No, it isn't planned.
And by the end of 2016 or in early 2017, Firefox won't be supporting any Plugins at all. All web browsers are in the process dropping "Plugins".
the-edmeister said
No, it isn't planned. And by the end of 2016 or in early 2017, Firefox won't be supporting any Plugins at all. All web browsers are in the process dropping "Plugins".
I hope that this is some really bad joke.
cor-el said
http://www.ghacks.net/2015/11/25/firefox-64-bit-to-support-microsoft-silverlight-after-all/ https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ https://blogs.oracle.com/java-platform-group/entry/npapi_plugin_perspectives_and_the
There was misunderstanding. the-edmeister wrote Firefox won't be supporting any Plugins at all which could mean that no more XPI extensions too.
XPI extensions has nothing to do with the end of support for NPAPI Plugins; two different types of add-ons.
According to this, Adobe Flash which uses NPAPI will be supported furthermore. I think NPAPI should be dropped completely, not partially.