Data returned from ajaxSetup dataFilter is not passed to ajax complete() callbacks

[jbabbitt]

The ajax complete() callbacks are passed xhr, but not the data returned from dataFilter.

As a result, dataFilter will not be applied to data loaded via the .load() function.

[dmethvin]

One solution would be to add settings (s) as an argument to the call to the complete handler in handleComplete.

[snover]

Resetting milestone to future.

[jaubourg]

​https://github.com/jquery/jquery/commit/5a721cf31b142365954a2d71e860534da4536b16

Forgot the damn # in the comment.

[james.m.greene@…]

This bug was never fixed. Or, it may have been fixed only for load but not for Ajax calls at large.

Fiddle: ​http://jsfiddle.net/JamesMGreene/CUJrN/

[JamesMGreene]

Requesting that this bug be reopened.

[dmethvin]

@jaubourg can you take a look?

[dmethvin]

In general it's better to create a new ticket than reopen an ancient bug. We need a Trac feature that freezes tickets more than a year old and prevents posts on them.

[jaubourg]

You should create a new ticket. Behaviour is consistent with what is documented. Your request is unrelated to ajaxSetup or the actual use-case involved here (title is still very misleading, original request was about applying dataFilter in ajaxSetting in the context of load as was determined with OP iirc).

It is obvious you wish the third parameter to be the success value. It is a feature request and should be in its own ticket for proper discussion. My take on it is that there are enough means to get the filtered data that we do not need to meddle with an already deprecated complete callback. You can call done on the jqXHR within the complete callback for instance.

[JamesMGreene]

@jaubourg: I'm perfectly fine with leaving it as-is if the complete callback actually get axed. Is there a targeted milestone release for that yet? It's already hung around much longer than I expected.

[jaubourg]

Replying to JamesMGreene:

@jaubourg: I'm perfectly fine with leaving it as-is if the complete callback actually get axed. Is there a targeted milestone release for that yet? It's already hung around much longer than I expected.

It will probably end up as one of these "deprecated but never removed" antics. complete is used for pretty much anything save for cooking breakfast. All we can do is show people how to handle stuff properly with 2 handlers or using always but the inconsistencies in signatures of the success and error callbacks makes complete so much more compelling in the "real world"(tm).