A failure has been detected to display Jmol when using the Chrome browser under MacOS.
The reason has been tracked down to a change of behavior in Chrome (and future versions
of Safari or other WebKit-based browsers) together with an old browser detection routine in
the Jmol.js library.
A new revision of Jmol.js has been made to avoid this problem, and will be included in the
next releases of Jmol, probably 12.0.30 and 12.1.33
Please stay alert for:
1. your existing pages stop working under Mac/Chrome
2. any unexpected misbehavior in your pages when you upgrade Jmol
(If you need to fix #1 but don't want to upgrade Jmol now, be welcome to contact me through
the jmol-developers list so we can forge a cure into your copy of Jmol.js)
I'm rather confident that nothing will be broken by applying the new version of Jmol.js to
existing pages, but one never knows. Particularly for singular combinnations of browsers and
OSs which I am unable to test.
The browser-checking page at the Jmol website will also be updated accordingly and should
now provide a more specific report of browser detection and what Jmol.js will do for inserting
JmolApplets for that browser.
If you see problems in your pages, please visit
and report a copy of that page so the problem can be recognized and fixed.
(The website might take some longer time to be updated, particularly so since the
SourceForge servers are experiencing problems these last days)
I realize that my previous message may sound too alarming, so I will be more specific.
The changes introduced into Jmol.js affect only the way the JmolApplets are inserted into the
page depending on the browser. So you just have to see if the applet shows up or not and if
Changes only affect Chrome, Safari and related, particularly under MacOS but also in part in
other OSs. There may be some change too for Firefox in MacOS