Skip to main content

Bug Tracker

Side navigation

#9782 closed bug (duplicate)

Opened July 08, 2011 09:41AM UTC

Closed July 15, 2011 05:25PM UTC

Last modified July 15, 2011 05:25PM UTC

error 'jQuery16206078858876646126_1310116245411 is not a function' after abort POST JSONP ajax-query

Reported by: anonymous Owned by: anonymous
Priority: low Milestone:
Component: ajax Version: 1.6.2
Keywords: Cc:
Blocked by: Blocking:


var p = $.ajax({ url : '', data : { part : 'test', v : 3 }, dataType : 'jsonp'});

setTimeout(function() {


}, 10);

Attachments (0)
Change History (5)

Changed July 08, 2011 01:20PM UTC by timmywil comment:1

component: unfiledajax
owner: → anonymous
priority: undecidedlow
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on 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 do not think jsonp can be aborted consistently across browsers. Once the script tag is on the page, some browsers will load the script whether you take the tag off or not.

Changed July 11, 2011 10:57AM UTC by Filatov Dmitry <> comment:2

When abort jsonp request you need no remove callback at once. If you replace callback at this moment something like this, you have no error:

window.jQuery16207753935731721285_1310374972748 = function() {

delete window.jQuery16207753935731721285_1310374972748;


Changed July 13, 2011 11:54PM UTC by dzearing comment:3

We are hitting this scenario as well in our scenarios.

If you abort a jsonp request, the response is still processed, causing a script error because the callback function was nuked.

Please fix this. Thanks.

Changed July 15, 2011 05:25PM UTC by jaubourg comment:4

resolution: → duplicate
status: pendingclosed

Changed July 15, 2011 05:25PM UTC by jaubourg comment:5

Duplicate of #8744.