From: A. H. <ang...@ua...> - 2011-01-27 09:04:27
|
Hello Kevin El 26 Jan 2011 a las 20:03, Kevin Rosso escribió: > I tried reporting this to mol...@li... but was sent a > rejection email. There's a 'J' missing there, maybe it was that: jmo...@li... > I've tried your live demo pages > (http://jmol.sourceforge.net/demo/#Interactive applet demonstration > pages) and I get the message: > "You do not have Java applets enabled in your web browser, or your > browser is blocking this applet. [...] > Does Jmol support Chrome? Yes, Chrome should be supported in Jmol. The rendering engine is Webkit, same as Safari. The browser detection routine in Jmol.js is old and does not take Chrome into account, that's what it says you are using Chrome (I've been checking this recently and was planning to upgrade the routine). But that browser misidentification should not be a problem for functioning. I think there are some ongoing changes in latest Chrome versions that are making some behaviours different to former version and to Safari. I've had similar problems recently while testing the new detection routine I was trying to implement. We will look into it. Thanks for reporting. It could also help if you tell us details of browser version and operating system, just in case. BTW, in my PC, Chrome 8.0.552.237 under WinXP is working fine for the Jmol pages. |
From: A. H. <ang...@ua...> - 2011-01-27 09:19:02
|
Sorry, a couple of typos slipped into my previous message: jmo...@li... is probably equivalent to jmo...@li... but I'm not sure. The first one is what I use regularly The browser detection routine in Jmol.js is old and does not take Chrome into account, that's what it says you are using ***Safari*** Your exact version of Java may also be relevant. I don't use Macs, but other users are knowledgeable about the quirks there. |
From: A. H. <ang...@ua...> - 2011-01-27 16:32:56
|
Clarifying Kevin's problem (some of the dialog between us went off- list): 1. in Mac OS Snow Leopard, same computer: - Chrome 8.0.552.237 (latest) fails to display Jmol applet - Safari 5.0.3 and Firefox 3.6.13 display OK (so it's not a Java problem, in principle, but something specific to Chrome itself or its relation to Java or the html tags) 2. - same version of Chrome works fine in my Windows PC so, not totally a Chrome problem either Maybe we can poll Jmol Mac users for this problem. Last month I observed something that may be related to this. I don't remember the exact details right now, but was related to some Chrome failure with either the <applet> or the <object> tag. And apparently Chrome behaviour had departed from Safari (not so updated it seems despite both running the Webkit engine) Jmol.js is currently inserting <applet> tags into Safari and Chrome vs. <object> tags for other modern browsers, due to some limitation in the browser detection that I was trying to improve-update. And I read on the web forums about such change in behaviour. I will post later more details about this. |
From: A. H. <ang...@ua...> - 2011-01-27 19:42:33
|
Kevin, I fund my former testing page. Let's see if we can corner the problem. Can you please test this page http://biomodel.uah.es/angel/Jmol/test/test-object-tags.htm and tell me which of the 4 Jmols you can see in Mac Chrome? |
From: Miguel H. <mi...@jm...> - 2011-01-27 19:52:25
Attachments:
Screen shot 2011-01-27 at 2.50.34 PM.png
|
Angel, Attached is the screen shot on my Mac with Chrome. Miguel 2011/1/27 Angel Herráez <ang...@ua...>: > Kevin, > > I fund my former testing page. Let's see if we can corner the problem. > > Can you please test this page > http://biomodel.uah.es/angel/Jmol/test/test-object-tags.htm > and tell me which of the 4 Jmols you can see in Mac Chrome? > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers > |
From: Kevin R. <ro...@gm...> - 2011-01-27 20:52:27
|
Hi Angel, I can see the middle 2 displayed on the page. The first one (inserted by Jmol.js) give me the error: "You do not have Java applets enabled in your web browser, or your browser is blocking this applet......" The second and third (<applet> tag and HTML4 <object> stripped of classid) are shown as gray and blue boxes (no molecule shown). The last does not render as I believe it's checking for IE. Hope this helps - 2011/1/27 Angel Herráez <ang...@ua...>: > Kevin, > > I fund my former testing page. Let's see if we can corner the problem. > > Can you please test this page > http://biomodel.uah.es/angel/Jmol/test/test-object-tags.htm > and tell me which of the 4 Jmols you can see in Mac Chrome? > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers > -- Kevin M. Rosso work: 202-687-3785 cell: 240-498-5896 |
From: Miguel H. <mi...@jm...> - 2011-01-27 20:57:43
|
Kevin & Angel, That is the same thing that I see on Mac Snow Leopard + Chrome. I tried to post a screenshot, but my image size was too big. Miguel On Thu, Jan 27, 2011 at 3:40 PM, Kevin Rosso <ro...@gm...> wrote: > Hi Angel, > I can see the middle 2 displayed on the page. > > The first one (inserted by Jmol.js) give me the error: > "You do not have Java applets enabled in your web browser, or your > browser is blocking this applet......" > The second and third (<applet> tag and HTML4 <object> stripped of > classid) are shown as gray and blue boxes (no molecule shown). > The last does not render as I believe it's checking for IE. > > Hope this helps - > > 2011/1/27 Angel Herráez <ang...@ua...>: >> Kevin, >> >> I fund my former testing page. Let's see if we can corner the problem. >> >> Can you please test this page >> http://biomodel.uah.es/angel/Jmol/test/test-object-tags.htm >> and tell me which of the 4 Jmols you can see in Mac Chrome? >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> Jmol-developers mailing list >> Jmo...@li... >> https://lists.sourceforge.net/lists/listinfo/jmol-developers >> > > > > -- > Kevin M. Rosso > work: 202-687-3785 > cell: 240-498-5896 > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers > |
From: A. H. <ang...@ua...> - 2011-01-27 21:05:02
|
Got Miguel's and Kevin's reports and screenshot. Thanks Will report back later or tomorrow (dinner time :-) ) |
From: A. H. <ang...@ua...> - 2011-01-28 09:11:19
|
Not sure what's going on. Jmol.js in inserting an applet tag (Jmol #1) for Chrome and fails to display, but when that code is written directly (Jmol #2) it works. I've read about changes in the way recent Chrome deals with object tags, but not with applet tags. And since Chrome/Win hasn't got this problem, I think that's not the issue now. Anyway, I'm trying to direct Jmol.js to insert object tag for Chrome and Safari instead of applet tag, let's see if that workaround solves the issue. Can you please test this new version http://biomodel.uah.es/angel/Jmol/test/test-object-tags-2.htm particularly under Chrome/Mac and Safari? Thanks |
From: Robert H. <ha...@st...> - 2011-01-28 14:34:37
|
I hope someone is filing a bug report with Chrome -- you have a good page there that very easily demonstrates the problem, it sounds like. 2011/1/28 Angel Herráez <ang...@ua...> > Not sure what's going on. > Jmol.js in inserting an applet tag (Jmol #1) for Chrome and fails to > display, but when that code is written directly (Jmol #2) it works. > > I've read about changes in the way recent Chrome deals with object tags, > but not with applet tags. And since Chrome/Win hasn't got this problem, I > think that's not the issue now. > > Anyway, I'm trying to direct Jmol.js to insert object tag for Chrome and > Safari instead of applet tag, let's see if that workaround solves the issue. > > Can you please test this new version > http://biomodel.uah.es/angel/Jmol/test/test-object-tags-2.htm > particularly under Chrome/Mac and Safari? > > Thanks > > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers > > -- Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 507-786-3107 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 |
From: Kevin R. <ro...@gm...> - 2011-01-28 14:30:44
Attachments:
Screen shot 2011-01-28 at 9.27.57 AM.png
|
Angel- I've tested your url and it now loads Jmol succesfully. Attached is screenshot. Would this qualify as a 'patch', were you to distribute the jar that generates this code? Let me know how to proceed. 2011/1/28 Angel Herráez <ang...@ua...>: > Not sure what's going on. > Jmol.js in inserting an applet tag (Jmol #1) for Chrome and fails to > display, but when that code is written directly (Jmol #2) it works. > I've read about changes in the way recent Chrome deals with object tags, but > not with applet tags. And since Chrome/Win hasn't got this problem, I think > that's not the issue now. > Anyway, I'm trying to direct Jmol.js to insert object tag for Chrome and > Safari instead of applet tag, let's see if that workaround solves the issue. > Can you please test this new version > http://biomodel.uah.es/angel/Jmol/test/test-object-tags-2.htm > particularly under Chrome/Mac and Safari? > Thanks > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers > > -- Kevin M. Rosso work: 202-687-3785 cell: 240-498-5896 |
From: Kevin R. <ro...@gm...> - 2011-01-28 15:00:52
|
I'm sorry , I meant distribute the Jmol.js that generates the correct code On Fri, Jan 28, 2011 at 9:30 AM, Kevin Rosso <ro...@gm...> wrote: > Angel- > I've tested your url and it now loads Jmol succesfully. Attached is > screenshot. Would this qualify as a 'patch', were you to distribute > the jar that generates this code? > Let me know how to proceed. > > > 2011/1/28 Angel Herráez <ang...@ua...>: >> Not sure what's going on. >> Jmol.js in inserting an applet tag (Jmol #1) for Chrome and fails to >> display, but when that code is written directly (Jmol #2) it works. >> I've read about changes in the way recent Chrome deals with object tags, but >> not with applet tags. And since Chrome/Win hasn't got this problem, I think >> that's not the issue now. >> Anyway, I'm trying to direct Jmol.js to insert object tag for Chrome and >> Safari instead of applet tag, let's see if that workaround solves the issue. >> Can you please test this new version >> http://biomodel.uah.es/angel/Jmol/test/test-object-tags-2.htm >> particularly under Chrome/Mac and Safari? >> Thanks >> >> >> ------------------------------------------------------------------------------ >> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! >> Finally, a world-class log management solution at an even better price-free! >> Download using promo code Free_Logger_4_Dev2Dev. Offer expires >> February 28th, so secure your free ArcSight Logger TODAY! >> http://p.sf.net/sfu/arcsight-sfd2d >> _______________________________________________ >> Jmol-developers mailing list >> Jmo...@li... >> https://lists.sourceforge.net/lists/listinfo/jmol-developers >> >> > > > > -- > Kevin M. Rosso > work: 202-687-3785 > cell: 240-498-5896 > -- Kevin M. Rosso work: 202-687-3785 cell: 240-498-5896 |
From: A. H. <ang...@ua...> - 2011-01-28 18:09:03
|
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 |
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 > |
From: A. H. <ang...@ua...> - 2011-01-28 20:17:32
|
Thanks, Oliver, for the report Pending further testing, this is my interpretation so far: 1. This is not an issue with browser handling of the applet tag, but with the object tag (I stand corrected here on my previous comment, after re-reading my own conclusions left in the wiki page last month :-) ) 2. There is a discussion on the web and many reports of websites suddenly failing due to Chrome's ~recent change of behavior over the object tag http://code.google.com/p/chromium/issues/detail?id=62076 which they say (a) will not be reversed --considered a spec, not a bug, (b) will propagate to Safari as it is updated The issue is with object tags using a classid='java: parameter. The cure is to remove this parameter (apparently the removal does not damage other browsers) 3. The reason the problem is only seen in Macs is due to the old browser sniffing code in Jmol.js --which incidentally I discovered last December, don't really remember why-- * So that Mac/Chrome is read as Mac/Safari and both get an object tag. * While Win/Safari and Win/Chrome are not detected and so get (as a fallback) an applet tag. * Win/Firefox and Linux/Firefox get object, but Mac/Firefox is set to use applet (don't know why). None of them give trouble. More details at the Wiki, http://wiki.jmol.org/index.php/Jmol_Applet/Browser_Support 4. My proposal (partially implemented in my v.2 page modified Jmol.js, which I would propagate to the official Jmol.js and the browser testing page in the Jmol website): a. Chrome is detected before Safari (although maybe that's not necessary). Or better, reduce browser sniffing to the (old) exceptions that were known not to work and leave most as feature detection. b. Both Chrome and Safari will get the object tag, irrespective of the OS, as other modern browsers are getting. c. Set Mac/Firefox to do the same as other Firefoxes (Anyone knows of any problems with Mac/Firefox that make the applet tag more adequate than the object tag?) d. Most importantly, adopt the new syntax for the object tag, so avoiding the problem seen in Mac/Chrome and a future problem in Mac/Safari |
From: Jonathan G. <gu...@uw...> - 2011-01-29 03:20:04
|
Angel, I found one problem with your proposal. See below. Jonathan On Jan 28, 2011, at 2:28 PM, Angel Herráez wrote: > Thanks, Oliver, for the report > > Pending further testing, this is my interpretation so far: > > 1. > This is not an issue with browser handling of the applet tag, but with the object tag (I stand > corrected here on my previous comment, after re-reading my own conclusions left in the wiki > page last month :-) ) > > 2. > There is a discussion on the web and many reports of websites suddenly failing due to > Chrome's ~recent change of behavior over the object tag > http://code.google.com/p/chromium/issues/detail?id=62076 > which they say (a) will not be reversed --considered a spec, not a bug, (b) will propagate to > Safari as it is updated > > The issue is with object tags using a classid='java: parameter. The cure is to remove this > parameter (apparently the removal does not damage other browsers) > > 3. > The reason the problem is only seen in Macs is due to the old browser sniffing code in > Jmol.js --which incidentally I discovered last December, don't really remember why-- > * So that Mac/Chrome is read as Mac/Safari and both get an object tag. > * While Win/Safari and Win/Chrome are not detected and so get (as a fallback) an applet > tag. > * Win/Firefox and Linux/Firefox get object, but Mac/Firefox is set to use applet (don't know > why). None of them give trouble. > More details at the Wiki, http://wiki.jmol.org/index.php/Jmol_Applet/Browser_Support > > 4. > My proposal (partially implemented in my v.2 page modified Jmol.js, which I would propagate > to the official Jmol.js and the browser testing page in the Jmol website): > a. Chrome is detected before Safari (although maybe that's not necessary). Or better, reduce > browser sniffing to the (old) exceptions that were known not to work and leave most as > feature detection. > b. Both Chrome and Safari will get the object tag, irrespective of the OS, as other modern > browsers are getting. > c. Set Mac/Firefox to do the same as other Firefoxes (Anyone knows of any problems with > Mac/Firefox that make the applet tag more adequate than the object tag?) Just tested this. Your version 2 page does not work with FF 3.6+ & MacOS 10.6. No Jmol appears in the first box. Apparently, MacOS FF does do something different. I will also test some of the other combinations this weekend. Jonathan > d. Most importantly, adopt the new syntax for the object tag, so avoiding the problem seen in > Mac/Chrome and a future problem in Mac/Safari > > > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers Dr. Jonathan H. Gutow Chemistry Department gu...@uw... UW-Oshkosh Office: 920-424-1326 800 Algoma Boulevard FAX:920-424-2042 Oshkosh, WI 54901 http://www.uwosh.edu/facstaff/gutow |
From: A. H. <ang...@ua...> - 2011-01-29 10:36:47
|
So I thought I had it right, now I'm feeling uneasy ;-) Jonathan reports: MacOS 10.6 and FF 3.6+: no Jmol appears in the first box, page v.2 Kevin reports: Mac OS X Snow Leopard and FF 3.6.13: ok The Mac/Chrome issue seems located and fixed, but now Mac/Firefox steps in! And as far as I can see 10.6 = Snow Leopard Could you all double-check, please? Also write down if the applet or object tags are being used (textarea at the bottom) Thanks, Angel |
From: A. H. <ang...@ua...> - 2011-01-29 17:04:06
|
On 28 Jan 2011 at 21:20, Jonathan Gutow wrote: > > c. Set Mac/Firefox to do the same as other Firefoxes (Anyone knows of any problems with > > Mac/Firefox that make the applet tag more adequate than the object tag?) > Just tested this. Your version 2 page does not work with FF 3.6+ & MacOS 10.6. No Jmol appears in the first box. Apparently, MacOS FF does do something different. I will also test some of the other combinations this weekend. Actually, this makes little sense. Box #1 is generated by Jmol.js; in page v.2, this is either an applet tag or a revised object tag, both of which are tested in boxes #2 and #3 which apparetly display ok So I'm inclined to think that Jonathan's test failed on #1 was coincidental. Otherwise, it's some failure in my Jmol_new.js I have move forward to a more extensive redesign of Jmol.js and that is now set as page v.3 http://biomodel.uah.es/angel/Jmol/test/test-object-tags-3.htm where Jmol.js will insert the revised object tag for almost any browser (change applies to Mac/Firefox, Mac/Opera) I have tested this v.3 on Macs using an online service at browsercam.com (yes, they run Java on their browsers!) and all display fine in Mac 10.4 or 10.5, Firefox, Safari or Opera So I think I'm going ahead with these changes to be put into the next releases of 12.0 and 12.1 I am also doing some review of the Browser Check page at the Jmol website, along similar lines and also to include better identification of browsers. Real browser reports are still welcome! |
From: Jonathan G. <gu...@uw...> - 2011-01-29 18:54:17
|
Angel, I agree my FF failure seems to be a one off. I restarted FF and all three pages now work with FF 3.6.13 and MacOSX 10.6.6. I will get and check a recent version of Chrome later today. I have to take advantage of the warm (22 F, -6 C) weather to do some tree trimming, so it will be a few hours. Jonathan On Jan 29, 2011, at 11:15 AM, Angel Herráez wrote: > On 28 Jan 2011 at 21:20, Jonathan Gutow wrote: >>> c. Set Mac/Firefox to do the same as other Firefoxes (Anyone knows of any problems with >>> Mac/Firefox that make the applet tag more adequate than the object tag?) >> Just tested this. Your version 2 page does not work with FF 3.6+ & MacOS 10.6. No Jmol appears in the first box. Apparently, MacOS FF does do something different. I will also test some of the other combinations this weekend. > > Actually, this makes little sense. Box #1 is generated by Jmol.js; in page v.2, this is either an > applet tag or a revised object tag, both of which are tested in boxes #2 and #3 which > apparetly display ok > So I'm inclined to think that Jonathan's test failed on #1 was coincidental. Otherwise, it's > some failure in my Jmol_new.js > > I have move forward to a more extensive redesign of Jmol.js and that is now set as page v.3 > http://biomodel.uah.es/angel/Jmol/test/test-object-tags-3.htm > > where Jmol.js will insert the revised object tag for almost any browser (change applies to > Mac/Firefox, Mac/Opera) > I have tested this v.3 on Macs using an online service at browsercam.com (yes, they run > Java on their browsers!) and all display fine in Mac 10.4 or 10.5, Firefox, Safari or Opera > > So I think I'm going ahead with these changes to be put into the next releases of 12.0 and > 12.1 I am also doing some review of the Browser Check page at the Jmol website, along > similar lines and also to include better identification of browsers. > > Real browser reports are still welcome! > > > > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers Dr. Jonathan H. Gutow Chemistry Department gu...@uw... UW-Oshkosh Office: 920-424-1326 800 Algoma Boulevard FAX:920-424-2042 Oshkosh, WI 54901 http://www.uwosh.edu/facstaff/gutow |
From: Jonathan G. <gu...@uw...> - 2011-01-29 21:50:41
|
Latest Chrome is working for me on MacOS X with version three page, but not version 1. Jonathan On Jan 29, 2011, at 11:15 AM, Angel Herráez wrote: > On 28 Jan 2011 at 21:20, Jonathan Gutow wrote: >>> c. Set Mac/Firefox to do the same as other Firefoxes (Anyone knows of any problems with >>> Mac/Firefox that make the applet tag more adequate than the object tag?) >> Just tested this. Your version 2 page does not work with FF 3.6+ & MacOS 10.6. No Jmol appears in the first box. Apparently, MacOS FF does do something different. I will also test some of the other combinations this weekend. > > Actually, this makes little sense. Box #1 is generated by Jmol.js; in page v.2, this is either an > applet tag or a revised object tag, both of which are tested in boxes #2 and #3 which > apparetly display ok > So I'm inclined to think that Jonathan's test failed on #1 was coincidental. Otherwise, it's > some failure in my Jmol_new.js > > I have move forward to a more extensive redesign of Jmol.js and that is now set as page v.3 > http://biomodel.uah.es/angel/Jmol/test/test-object-tags-3.htm > > where Jmol.js will insert the revised object tag for almost any browser (change applies to > Mac/Firefox, Mac/Opera) > I have tested this v.3 on Macs using an online service at browsercam.com (yes, they run > Java on their browsers!) and all display fine in Mac 10.4 or 10.5, Firefox, Safari or Opera > > So I think I'm going ahead with these changes to be put into the next releases of 12.0 and > 12.1 I am also doing some review of the Browser Check page at the Jmol website, along > similar lines and also to include better identification of browsers. > > Real browser reports are still welcome! > > > > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers Dr. Jonathan H. Gutow Chemistry Department gu...@uw... UW-Oshkosh Office: 920-424-1326 800 Algoma Boulevard FAX:920-424-2042 Oshkosh, WI 54901 http://www.uwosh.edu/facstaff/gutow |
From: Jonathan G. <gu...@uw...> - 2011-01-29 23:30:30
|
Linux testing: Version 3 page Chromium-OK Epiphany-OK FF-OK Midori-OK NetSurf-No good-appears not to support javascript SeaMonky-OK Conkeror-OK Drooble-No good-again may not support javascript at all. This looks pretty good to me. Jonathan On Jan 29, 2011, at 11:15 AM, Angel Herráez wrote: > On 28 Jan 2011 at 21:20, Jonathan Gutow wrote: >>> c. Set Mac/Firefox to do the same as other Firefoxes (Anyone knows of any problems with >>> Mac/Firefox that make the applet tag more adequate than the object tag?) >> Just tested this. Your version 2 page does not work with FF 3.6+ & MacOS 10.6. No Jmol appears in the first box. Apparently, MacOS FF does do something different. I will also test some of the other combinations this weekend. > > Actually, this makes little sense. Box #1 is generated by Jmol.js; in page v.2, this is either an > applet tag or a revised object tag, both of which are tested in boxes #2 and #3 which > apparetly display ok > So I'm inclined to think that Jonathan's test failed on #1 was coincidental. Otherwise, it's > some failure in my Jmol_new.js > > I have move forward to a more extensive redesign of Jmol.js and that is now set as page v.3 > http://biomodel.uah.es/angel/Jmol/test/test-object-tags-3.htm > > where Jmol.js will insert the revised object tag for almost any browser (change applies to > Mac/Firefox, Mac/Opera) > I have tested this v.3 on Macs using an online service at browsercam.com (yes, they run > Java on their browsers!) and all display fine in Mac 10.4 or 10.5, Firefox, Safari or Opera > > So I think I'm going ahead with these changes to be put into the next releases of 12.0 and > 12.1 I am also doing some review of the Browser Check page at the Jmol website, along > similar lines and also to include better identification of browsers. > > Real browser reports are still welcome! > > > > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Jmol-developers mailing list > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-developers Dr. Jonathan H. Gutow Chemistry Department gu...@uw... UW-Oshkosh Office: 920-424-1326 800 Algoma Boulevard FAX:920-424-2042 Oshkosh, WI 54901 http://www.uwosh.edu/facstaff/gutow |