Some Additional Information (Windows 7):
1) Chrome is becoming a bit of a nuisance re Java - OK, that was editorial.
2) Chrome supplies some command line line switches to turn off features, including the the Java version police (editorial sarcasm). In my hands the Java related command line switches do not work:
3) I updated both Chrome and Java to the latest versions. I still got the Java version warning buttons.
4) I repeated 3 above using Chrome as the upgrade vehicle for Java. It turns out that this route produces a small Chrome application for Java update. No luck - same final result as 3 above.
5) There is now a button (latest Chrome) that says "Always run on this site." That seems to work, but there is no reason for this Java block in the first place. I have that latest version of Java and the applet that Chrome finally loads verifies this fact.
6) Now a real bummer from my perspective. Even with the signed applet, updated Java (higher than 1.6.0_21) will not allow applet access to files on a localhost server. This has to be driving other page developers nuts!
The Chrome Java version blocker (AKA the Java police - sorry!) is NOT a Jmol problem. I see it on all of the applets I try to access. Jay, Angel is correct. You need to check which problem you are encountering. The corrected Jmol/Chrome/applet-tag problem or the Chrome Java version blocker.
Just as a point of information, I tried liberalizing Windows security settings on the localhost Web site - i.e. anybody can do any thing! No luck, Java higher than than 1.6.0_21 will not allow an applet to read a file via the localhost server.
Department of Chemistry
Illinois State University
Normal, IL 61790-4160
From: "Angel Herráez" <angel.herraez@...>
Sent: Saturday, May 07, 2011 6:49 AM
To: osrothen@..., jmol-users@...
Subject: Re: [Jmol-users] google chrome under jre 1.6.24
Otis knows better abaout this, but there is a chnce that your problem may not be his.
There have been changes in Chrome support of the APPLET tag, and that has been fixed
recently in Jmol.js. So, it's important that you check and tell us
1- what is your OS
2- do you see the applets using other browser?
3- what is the Jmol version you are using (newer Jmol.js includes the fix)