Ok here is the deal IE sucks. Everything about the bowser sucks. From the buttons to the speed to the debugging. IT ALL SUCKS!
Now for what I have found.
It seems like for some reason the IE just cannot do anything correctly. Your site funnyballs.com
kills not only IE but takes down my new debugger (made by Microsoft of course). Your code does not warrant a complete death blow to IE, IE just cannot handle it.
This really does not seem to have anything to do with mootools, Joomla 1.5, Sobi2, javascript, WYSIWG tinymce. Even mixed they seem to work fine together. It has everything to do with how IE handles exceptions, errors, etc.
So what is the cause?
Here is an article to better explain it:
http://clientside.cnet.com/code-snippets/manipulating-the-dom/ie-and-operation-aborted/So
thatch10 I need you to comment out ja.cssmenu.js and see if that helps. That will probably kill your suckerfish menus. If you can, try creating a hard code link on the front page to "Add Entry" to test it out. My debugger is put to a death blow by this line
if (window.attachEvent) window.attachEvent("onload", sfHover); in that file.
If you are brave you could try replacing the line in RED with the following:
window.addEvent('domready', function(){
sfHover
});
Window.addEvent is mootools way of waiting after the DOM is ready to load your suckerfish menus.
Quote:
"In my experience, this error is encountered when one writes code that tries to do things before the page is ready - inline javascript or something like that. You should avoid document.write entirely. You should avoid innerHTML entirely (and use things like Mootools setHTML method to avoid memory issues). " This is not my quote it was taken from Aaron over at the site that is posted above
I pray that makes sense and it helps you somewhat!
Cheers!
