> What I am saying is this: Suppose they updated Safari and tested it on > the old java code. It worked. They then updated java (but did not > test it ??).
Of course, that *should not* happen ... but it looks like it may have :-) > It may be that the update to java is fine as evidenced > that it works with other browsers (with the patch applied, whatever it > does), but there was something in safari that was inconsistent with the > new java update and did not get tested. Thus is the problem with java > or safari? The problem is in LiveConnect ... which is the interface between Safari JavaScript and Java. And that is the problem ... it falls through the cracks. That is why Apple was late in releasing LiveConnect support in Safari and that is why it is currently broken. The Mozilla browsers probably work because they have their own LiveConnect implementation. Miguel ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Jmol-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-users
