Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsFiddle.net that reproduces the issue experienced to help us assess your ticket.

Additionally, test against the jQuery (edge) version to ensure the issue still exists.

I don't doubt this is a problem. I've seen many times where adding a dummy catch is necessary to avoid IE errors, but a test case to confirm would be helpful. L#57 of current deferred.js.

Forgot to mention, the exact IE error is:

Exception thrown and not caught

Replying to [comment:1 timmywil]:

>...but a test case to confirm would be helpful.

Of course. If I can make the time this weekend I'll try to put a reduced test case on jsFiddle.

However there is a point about the difference in the two try{} finally{} statements currently in use. If one needs catch(pseudoError){} to avoid errors in IE, chances are the other would need that too, at least for consistency's sake.

#9246 is a duplicate of this ticket.

Bug mentioned already here

http://webbugtrack.blogspot.com/2007/11/bug-184-catch-to-try-catch-finally-in.html

I get it in IE8 on XP in jQuery 1.6.1 unless I add a catch here:

// resolve with given context and args
resolveWith: function( context, args ) {
  if ( !cancelled && !fired && !firing ) {
    // make sure args are available (#8421)
    args = args || [];
    firing = 1;
    try {
      while( callbacks[ 0 ] ) {
        callbacks.shift().apply( context, args );
      }
    }
    catch(e) {}
    finally {
      fired = [ context, args ];
      firing = 0;
    }
  }
  return this;
},

Missed the message:

Unexpected call to method or property access.
Line: 5569
Char: 5
Code: 0
URI: http://code.jquery.com/jquery-1.6.1.js

does this still need a test case to move from pending?

Hi, Please see : http://jsfiddle.net/r7MgY/6330/

Please, fix the bug. Please, notice that it is not a feature request.

#9517 is a duplicate of this ticket.

Add catch block to try/finally in deferred. Fixes #9033. Test case needed.

Changeset: 0a80be67f4fe968d99777564a02aeddbde1fbf35

Revert "Add catch block to try/finally in deferred. Fixes #9033. Test case needed." Line of exception was lost when debugging.

This reverts commit 0a80be67f4fe968d99777564a02aeddbde1fbf35.

Changeset: 39a2f29c29fdb296bb178b3c55d805ea0dc2f0ce

Fix was reverted, but I hear jaubourg has a fix for this when $.Callbacks is introduced in 1.7.

#9718 is a duplicate of this ticket.

Looked at this further. The try{} finally{} seems to be triggered only on script parse errors. For example I had a stray comma at the end of an object definition (as you probably know FF and WebKit silently ignore these but IE throws an error on loading the script).

In that terms I'm not sure if the whole try{} finally{} is needed there as it may let unparsable scripts to go unnoticed. On the other hand jQuery silences most JS errors, so why not these...

#9878 is a duplicate of this ticket.

#9993 is a duplicate of this ticket.

#10030 is a duplicate of this ticket.

#10162 is a duplicate of this ticket.

#10181 is a duplicate of this ticket.

There is no try/finally block in the new $.Callbacks code. Deferred objects are "locked" if and when an exception occurs in a callback.

Related commit: https://github.com/jquery/jquery/commit/4092e3d2754e3847cd3159edb23184d4cfd4cf03

#10348 is a duplicate of this ticket.

#10428 is a duplicate of this ticket.

#10508 is a duplicate of this ticket.

#11193 is a duplicate of this ticket.

#11197 is a duplicate of this ticket.