Hello Nick Thanks for reporting. I think this is a known issue with newest Chrome versions that I tried to fix recently. The fix is in Jmol.js, and it seems that the pages you have tested are using different versions of that.
> For examplehttp://chemapps.stolaf.edu/jmol/docs/examples-11/new.htm That uses Jmol 12.1.31 with Jmol.js 12.0 4/5/2010 > as ishttp://chemapps.stolaf.edu/jmol/docs/examples-12/new.htm And that uses Jmol 12.1.36_dev with Jmol.js 12.0 1/31/2011 The latter includes the key text: // ah 1/2011 -- wider detection of browsers; more browsers now use the object tag instead of the applet tag; // fix of object tag (removed classid) accounts for change of behavior in Chrome So I think that's it: latest Mac-Chrome needs the new Jmol.js It only affects MacOS (a limitation of the way the browser detection was implemented in old Jmol.js, together with a change in behaviour of WebKit in recent versions; should also affect Safari soon) ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
