2012-08-28 14:06 Europe/Helsinki: Angel Herráez: >> Example: http://biomodel.uah.es/Jmol/JSO/simpleJmol3-0.htm > > That's my page. Be careful, since I am not sure what set of files that is > using > (I cannot update the site now from where I am). I think that 3-0 page was > using the standard JS files included in Jmol distribution, but maybe I > changed them with some of Bob's fixes along my prevous discussion. Be > sure to test also with Jmol 13.0 as you are doing.
OK. I was pointing to that page as an example about somebody else using Jmol-JSO and hitting the same issue with Google Chrome. I didn't know it was you. >> To view the issue, open the URL above in Google Chrome (I tested >> 22.0.1229.14 beta and 23.0.1246.0 canary), press F12 and select Network. >> Reload the page and grant permission to run Java applet. Notice that >> Jmol-JSO library causes extra request for JmolApplet.class for each Jmol >> view. > > So is this a Chrome-only issue? At least I have only seen it with Google Chrome. >> The 'params.code' causes Chrome to blindly trying to load the >> JmolApplet.class from the codebase path. > > I think that the setting of params.codebase and params.code has always > been like that, and that's how the applet is expected to be initiated. What > happens if you try using Jmol.js intsead of JSO? I haven't tested that because I'm (at least currently) using features provided only by JSO version. > Maybe it's restricted to HTML5 as you say, I've only started to use this > doctype recently. It seems that (at least with HTML5 doctype) chrome applies following logic if all following "params" are set: - archive - codebase - code Then proceed trying to load URI codebase+code and if that fails, try to load codebase+archive and then initiate class pointed by code within the archive. I have no idea how to start the code without Chrome trying to load the codebase+code URI first. >> if the user agent is some variant of Internet Explorer because it >> guarded by a following test: >> >> if (Jmol.featureDetection.useIEObject >> || Jmol.featureDetection.useHtml4Object) > > Shouldn't be that. Chrome will fall into the "useHtml4Object" filter. No > worries > about IE-specific code. OK. The variable naming misguided me a bit. -- Mikko
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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 threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
