From: Oliver S. <rev...@us...> - 2011-01-28 19:53:08
|
Angel, I'm happy to report: OS: Ubuntu Linux 10.4 (x64) with Sun-Java: 1.6.0_22 : * Chrome 8.0.552.237 - page v.1 and v.2: Jmol-Applets 1,2 and 3 work * Firefox 3.6.13 - page v.1 and v.2: Jmol-Applets 1,2 and 3 work OS: Windows 7 (x64) with Sun-Java: 1.6.0_22 (x86): * Chrome 8.0.552.237 - page v.1 and v.2: Jmol-Applets 1,2 and 3 work * Firefox 3.6.13 - page v.1 and v.2: Jmol-Applets 1,2 and 3 work * Internet Explorer 8 (x86) - page v.1 and v.2: Jmol-Applets 1,2, 3 and 4 work (no screen-shots as they all basically look like Kevin's "Screen shot 2011-01-28 at 9.27.57 AM.png") Oliver 2011/1/28 Angel Herráez <ang...@ua...> > > Bob, > problem is, I don't know what/where the "bug" is, so I can hardly file it --may be taken as a > Jmol.js problem. As I said, the applet code (#2) works fine when entered manually, but not > (#1) when entered by Jmol.js (on my v.1 page, using the regular Jmol.js) > http://biomodel.uah.es/angel/Jmol/test/test-object-tags.htm > > On page v.2, I am using a modified Jmol.js > http://biomodel.uah.es/angel/Jmol/test/test-object-tags-2.htm > It basically directs Chrome and Safari to use an obejct tag instead of an applet tag. Since the > strange behaviour seems related to Mac/Chrome's interpretation of the applet tag (given the > difference Kevin sees between my v.1 and v.2 pages), the problem is not solved but skipped. > > Kevin, > yes, given that the modified Jmol.js works it will be put into the next distribution of Jmol (but > I'd like to have some more extensive testing by different users, browsers and OSs before > releasing it) > > For now, I will send the modified Jmol.js to you off-list if you want, > as soon as I double-check which were the changes I introduced (this was done back at the > beginning of December). > BTW, I documented some of those findings and proposed changes at > http://wiki.jmol.org/index.php/Jmol_Applet/Browser_Support > |