I tought I had avoided to rely on many browser-specific tricks when I reviewed Jmol.js last January. I certainly left the parts related to checking old versions of browsers, but those should never ve reached actually now.
I guess the problem is with webpages that use not updated versions of Jmol.js We run into that recently with Chrome (I think even in Proteopedia) An update or a patch in Jmol.js should fix the issues, but that relies on the page author. > Andreas, what's the rest of that message? > > msg = "Your web browser is not fully compatible with Jmol\n\n" + > "browser: " + browser + > " version: " + browserVersion + > " os: " + os + > " isBrowserCompliant: " + isBrowserCompliant + > " isJavaCompliant: " + isJavaCompliant + > "\n\n" + ua; > > > That will tell us what's coming up short. Please go to http://jmol.sourceforge.net/browsercheck/ which I updated to take better care of newer browsers ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
