jQuery "Exception thrown and not caught" error in IE8

Alright I've seen this particular proble开发者_C百科m a couple of times here on SO, but it all didn't solve my case. Here's the website we are talking about: http://kwestievan.nl/unityexpress

Open in IE7/8 and don't mind any CSS errors that might be there.

If I look at the console I see "Exception thrown and not caught" on line 1011 of jquery.js (1.6.2). I take it that this has nothing to do with jQuery but with my own code, but I have no clue where to start. I might do something wrong in my code but the console doesn't give a hint at all. All other browsers don't have a problem with the code as it is now.

Can somebody help me?

---

I had a similar issue, seeing an "Exception thrown and not caught" error in IE8 (while in IE7 mode) using jQuery 1.6.4.

The stack trace started in the finally clause in jQuery's resolveWith() and went through ready() and doScrollCheck() only, but the problem was in my code, executed via $.ready().

I found the problem in my code, which was actually an "Object does not support this property or method" error, only by commenting out code until I could find the offending line, and then running that line in the console.

I think that the try {} finally {} block in jQuery's resolveWith() may have been masking the source of the error. I'm not sure, but if I had to debug it again I might try:

• moving my code outside of $.ready(); or
• in a local copy of jQuery, adding a catch (e){} clause in resolveWith() to inspect the error

---

I just had this same error with jQuery UI tabs in IE only(version 8). As it turns out, I had invalid HTML on which FF and Chrome gave me a pass. Not so with IE.

I discovered this by running the HTML validator which pointed to an HTML error (I had an extra quote on a DIV id). I fixed this error and the js error message went away in IE.

---

You should enable JavaScript debugging in your "Internet Options." or in your developer tools for IE. The code should "break" on the line that is giving you problems, and then you can inspect the call stack to see which of your code triggered the problem.

---

Thanks for the tips. I solved this by removing the ":nth-of-type()" jQuery selector which seemed to choke IE8.