Surprisingly enough, I'm already having issues with IE9. I'm on 64-bit IE9, but I don't know how much that matters. I use a jQuery plugin called Fancybox (http://fancybox.net) on a couple of websites, and when I load fancybox.net or any of the sites containing fancybox, I get this error:
This error appears not only on this page, but ironically even msn.com kicks this error on page load in IE9. I'm completely new to the JS debugger in IE, but it seems to me that this may be a jQuery issue, based on what I was able to decipher from IE's debugger. I did a lot of googling on the matter yesterday, and wasn't able to find anyone with the exact same issue as me, so it could possibly be a browser setting issue???
From what I did find, I know jQuery 1.5 had issues with IE9, but from what I read, most issues were solved when updating to jQuery 1.5.1. On the page that I'm testing offline that is giving me problems, I've tried jQuery 1.4.4 and 1.5.1 and neither solves my problem. What is happening is that if I have an image that should lightbox upon clicking, clicking does nothing except pushing the line 72 error I've been seeing a lot of. I would think that clicking should at the very least load the image without the lightbox, as though no js was being used. This error I'm seeing is not limited to the Fancybox plugin. I use the Lytebox (http://www.dolem.com/lytebox/) plugin, and when testing a site using Lytebox, I get the line 72 error again, but at least it lets me click through to the un-lightboxed image. Even jQueryUI's demo pages have been problematic on IE9 for me. Some of the effects work, while some do not.
I apologize, because my javascript knowledge is lacking, but I'm reading through jQuery Novice to Ninja, along with online tutorials, to try to learn some more on the subject. My current js knowledge includes downloading jQuery and using an already developed and tested plugin to achieve my goal, but I am working to change that.
I've posted this in the Fancybox forum, along with a few others, in the hopes that someone else has already solved some of these issues I've seen with IE9.