Thanks for the links, Dave. #3984 should be fixed in new implementation and I just comitted a patch that takes care of #5280. I also moved code around to handle a problem discussed in dojo: http://trac.dojotoolkit.org/ticket/9486
Still, doesn't answer my initial question though I'm quite happy to fix things as I refactor. Priority is now to rethink the transport binding so that we don't need a global transportSelector. Things would be perfect without specificities that come from jsonp support and make things quite intricate. 2009/12/5 Dave Methvin <[email protected]> > > While refactoring $.ajax, I realized aborting a request doesn't fire > > complete. While this could make sense for early abort (beforeSend) since > > ajaxStart hasn't been fired yet, it is quite awkward later on when > timeout > > does fire the event while being nothing more than an automated abort. > > There is a ticket kind of related to this having to do with ajaxStop: > > http://dev.jquery.com/ticket/3984 > > Also this ticket related to aborting requests when leaving a page in > IE: > > http://dev.jquery.com/ticket/5280 > > It probably wasn't intentional the way it is now, just an edge case > that wasn't fleshed out. > > -- > > You received this message because you are subscribed to the Google Groups > "jQuery Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<jquery-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/jquery-dev?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
