Ho, ho! Looks like the Oracle guidelines are changing every day. This one
in our favor. I have added the following line to the manifests inside the
Jar files:
Caller-Allowable-Codebase: *
and I do believe that gets rid of the warning messages.
Test of trusted-signed certificate for the full Jmol build
http://chemapps.stolaf.edu/jmol/jsmol/test2.htm?SIGNED
Q: Did you get a warning message at all?
Q: How many warning dialogs do you get? Of what nature?
Q: If you reload the page does it still ask you to approve? Same number of
times?
Q: If you close your browser and reopen it and go to the page, any
differences there? (Back to asking all the questions, or no questions, or
fewer?)
Q: If you *go to another browser *do you get that message? Or is it
completely gone now?
Bob
--
Robert M. Hanson
Larson-Anderson Professor of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
