1.6 My Account login display error in Google Chrome

[Jeremy Buhler]

When using Google Chrome on Windows XP the 1.6 OPAC 'My Account' page does not always load or display completely (screenshot attached). In tests on Sitka, Conifer, and Indiana OPACs the username and password fields are sometimes completely missing. Reloading the page sometimes fixes the problem, but not in an obvious pattern. Tested on default skin (Sitka and Conifer) and Craftsman (Indiana). The page loads correctly on the openils 1.2 public testing OPAC.

[Dan Scott (denials)]

We see this a lot; not just on My Account, but on almost any page. I strongly suspect it is due to a bug in Dojo, perhaps complicated in Evergreen by mixing the Dojo event model with our legacy JS event processing model.

Anyway, see:

  * http://bugs.dojotoolkit.org/ticket/10811
  * http://stackoverflow.com/questions/2164028/dojo-fails-to-load-from-googles-cdn-using-chrome-produces-uncaught-illegal-acce
  * http://trac.dojotoolkit.org/ticket/9659

For what it's worth, I also used to see this a lot in Firefox - but swapping in dojo.js from Dojo 1.4.2 (where bug 9659 was fixed) enabled me to click through more than 75 results in Firefox 3.5 on Linux without seeing the aborted screen of death... which was pretty much guaranteed to happen every 25 requests or so with the Dojo 1.3.2 version of dojo.js.

It looks like Dojo 1.3.3 was released on March 10, 2010, so perhaps it has the same fix in a more-compatible version of Dojo with our use in Evergreen 1.6...

[Dan Scott (denials)]

Ah, and here's the Firefox-relevant Dojo bug that I was reading about previously: http://bugs.dojotoolkit.org/ticket/8976

[Dan Scott (denials)]

Quick testing with dojo.js from Dojo 1.3.3 suggests that it resolves our Firefox problems (after 25 pages), but I'm still seeing the same "Uncaught illegal access" JavaScript console errors with aborted screens in the Chromium-on-Linux nightly build.

[Michael Peters (mrpeters)]

Since we're now using Dojo 1.3.3 for new installations I'm going to mark this as 'Fix Committed' . for those still experiencing, it sounds like upgrading Dojo to 1.3.3 is the solution.