JmolCore.js uses a completely different method and definitely tests for Mozilla first.

That's something we could change, but I like it that way, and right now I'm not planning to do any changes at all to Jmol.js and do not plan to adapt Jmol.js further. Unless you find that pages loaded using MSIE are broken with Jmol.js, I advise not changing it.

We should probably try to track down some older versions of MSIE -- this gets hard to do! -- and see that works (probably the best test).


On Tue, Jun 5, 2012 at 2:30 PM, Angel HerrŠez <> wrote:
Sorry to be a pest, but no.

Jmol.js at least tests for MSIE before testing for Mozilla.

See it at †

Also, because of testing for "compatible" in the UA, even if we check
"mozilla" first it will still be classified as IE.

I think we need to check IE version <=9 at the same time as >=5.5 in order to
define "msie" object tag.
Or wholly rework the browser detection routine in Jmol.js --which I think it's
not the time to do.

I haven't checked carefully, but on first inspection I got the feeling that the
new JmolApplet.js and †JmolCore.js are using the same routine.

On 5 Jun 2012 at 13:31, Robert Hanson wrote:
> Ah, yes. I see. Well, MSIE 9.0 reports navigator.userAgent to be "Mozilla", so that takes care of
> that!

Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
Jmol-developers mailing list

Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Chemistry Department
St. Olaf College
Northfield, MN

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