>>Unfortunately, I do not have the exact number ... and the system was >>subsequently upgraded to 10.4 Tiger with Safari 2.0.1 (after updates) > > For what it's worth, I have one machine I have left with 10.3.9 and > Safari 1.3.1 (v 312.3.1) which renders the applets marked up in an > object tag, accessible from my test pages at: > <http://doolittle.ibls.gla.ac.uk/leader/NewInclusionTests/> > This may mean that people who have not upgraded to Tiger but have the > latest version of 10.3 and Safari 1.3 may be able to use the object > tag.
I have the following concerns: I cannot distinguish between 312.3 and 312.3.1 ... so what is the behavior of 312.3 ? I think that Safari 2.0 started their internal version number at 400. Are there numbers in the 400 series that do not work? If so that complicates the task a little, because the test must become >312.3 but <400 ... if indeed they started at 400. What is the problem with letting this version of Safari use <applet> tags? >>Is it possible that you have a cache problem? > > Sorry. Must have been the central Uni cache which can take a day to > clear as it's OK this morning with my test page at: No problem. Miguel ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
