CUNY Academic Commons

I tried on another computer and it was fine. So maybe it is the computer. And I did not hear any complaints from the students. So just disregard this report.

Matt's idea is a good one, if you still find problems. And if that doesn't work - maybe you can you switching the "Animate the page menu bar with Javascript" in Atahualpa's Menu 1 (Page Menu) option. Just curious if that will have any effect.

Does it seem like it works better after the page gets loaded? I thought saw what you were talking about initially, but after awhile, the sub-menus seem to be working for me ok. I am on Firefox.

I found this problem on a computer at my office on Explorer. I could not even click a submenu. It just run away - closed. At my home computer, it was better on Chrome and Firefox. At least, I can find a way to get into a sub-menu. I took Scott's advice just now and said "NO" to "animate the page menu bar with Javascript" and the submenu stayed like before (before the upgrade). So I think it is fine right now. But I am going to check the computer at my work to see. Thanks, Matt and Scott.

Okay. Let's leave this ticket open until we figure this out. Obviously, we want the site to be navigable to people no matter what browser they're using.

I just tried in Internet Explorer and it doesn't seem to work. And I notice that at the bottom of the page, the status bar reads "Done, but with errors on the page." So I wonder if there are some javascript errors going on with IE?

But now, upon review - after waiting a bit - it seems to work (even though the message on the status bar remains). Maybe you were changing things in your settings when I was testing? Or is it taking a long time for your script to load, for some reason, and then it starts to work. Do you experience this?

I experience the same thing in Safari and Chrome - it does not work initially (although the page seems to be fully loaded) - but after awhile - the menus work fine. Actually Chrome took a long time to work, Safari not much.

Just wondering - did you changed the "Javascript: External file or inline?" option. I believe it defaults to "inline," which is what it should be.

Javascript and CSS are both set as "inline". The loading time is long, I think it is because I have calendar and Twitter widgets, especially calendar widget. When I get into pages, the loading time is longer, because I embedded videos. I think the problem is on IE. It is still very hard to get to the sub-menu. I have no problem now with Chrome and Firefox. Thanks, Scott.

I'm confirming that the JavaScript version is pretty much completely broken in IE. Is this IE's fault or Atahualpa's fault? Probably a little of both.

It would take me hours to debug and fix these problems, especially because JS-in-IE is not my strong point. Because the non-JS version is working fine, I am tempted to put this in the won't-fix pile. Any objections?