We are hoping to use JavaPlugin2 from Apple as the official Java for Mac OS X on the 1.9.3 branch (replacing JEP). JEP is being ported to NPAPI by Steven Michaud in case JavaPlugin2 is not ready in time. This bug is for tracking Apple's JavaPlugin2 progress. We should post on this bug: 1. Notes on when new preview releases become available. 2. Apple bug numbers for bugs in JavaPlugin2 that we have reported to Apple. As of now, the most recent Java preview from Apple including JavaPlugin2 is: "Java for Mac OS X Developer Preview 10M3044+9M3144" released on March 19, 2010 for Mac OS X 10.5 and 10.6, available to ADC seed members.
A new developer preview version is available, released on April 14, 2010: "Java for Mac OS X Developer Preview 10M3050+9M3150" "Updates Java SE 6 to 1.6.0_19 on Mac OS X 10.6 and 10.5, and updates J2SE 5.0 to 1.5.0_24 on 10.5." Reference: http://lists.apple.com/archives/java-dev/2010/Apr/msg00065.html
Another developer preview was made available today: Java for Mac OS X Developer Preview 10M3064+9M3164 "Updates Java SE 6 to 1.6.0_20 on Mac OS X 10.6 and 10.5, and updates J2SE 5.0 to 1.5.0_24 on 10.5."
(In reply to comment #2) > Another developer preview was made available today: > > Java for Mac OS X Developer Preview 10M3064+9M3164 > > "Updates Java SE 6 to 1.6.0_20 on Mac OS X 10.6 and 10.5, and updates J2SE 5.0 > to 1.5.0_24 on 10.5." Now this version is officially released: http://support.apple.com/kb/HT4141 http://support.apple.com/kb/HT4140
The new updates can be downloaded from: http://support.apple.com/kb/DL972 http://support.apple.com/kb/DL971
I haven't been able to get it Java to run in Minefield for at least a month now. Seeing as you have it running, I decided to try it with a new profile, and that worked. I suspect it's either an about:config option I've modified, or an addon conflicting. Is there any way to debug this without going through each and every about:config option/addon, disabling them and seeing what effect they have? (I have quite many addons, but it's probably not that hard to figure out which is the likely culprit in this case, so I'll start by going through those right now.)
(In reply to comment #5) Apple's Java Plugin2 was unusable on the trunk from the firefox-2010-04-06-03-mozilla-central build through the firefox-2010-05-13-03-mozilla-central build due to problems on our side (bug 528146). Furthermore, it's only the most recent versions of Java Plugin2 (in Update 7 for OS X 10.5 and Update 2 for OS X 10.6) that work on the trunk even now (since the patches for bug 556092 landed on 2010-04-05). For more information see bug 563731.
> Apple's Java Plugin2 was unusable on the trunk from the > firefox-2010-04-06-03-mozilla-central build through the > firefox-2010-05-13-03-mozilla-central build due to problems on our > side (bug 528146). Java Plugin2 was unusable on the trunk only on OS X 10.6.X -- since only there do we try run it out of process (even the part that normally runs in process).
So, it seems the add-ons AdBlock Plus and Greasemonkey separately causes Java not to run. At least not with my configuration, which is the following: Mac OS 10.6 The standard OOPP about:config settings (that is, running JavaPlugin2 out of process) And the the setting in the Java-settings panel itself, set to running inside the browser process. When the add-ons mentioned above are disabled, this configuration works with simple Java applets, but seems to fail at more advanced applets like http://minecraft.net/play.jsp. After loading the files, the applet just remains black. About my configuration above, I'd like to ask, is this the correct one? I think I've tried with all possible combinations, but if not, which ones are you supposed to have if you use the latest nightly builds on 10.6?
Magne, thanks for your report. Please open a new bug on this and make it depend on this bug (bug 554103). Also cc me on the bug.
(Following up comment #9) Actually, you should probably open more than one bug -- one for the issue with AdBlock Plus and Greasemonkey, and another for the issue with http://minecraft.net/play.jsp. Before you open a bug on the http://minecraft.net/play.jsp issue, check through this bug's dependencies to make sure it's not a dup.
All dependent bugs was RESOLVED, so I'm also marking this as one it could be also marked as WONTFIX per bug #1269807 ( https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ )