[4.1.1 rc1] Ext.Ajax.abort() does not abort the request in Chrome

**anton.dimitrov** · 7 May 2012 5:50 AM

REQUIRED INFORMATION Ext version tested:

Ext 4.1.0
Ext 4.1.1 RC1 (4/30)

Browser versions tested against:

Chrome (18.0.1025.168 )
IE9
FF3

DOCTYPE tested against:

<!DOCTYPE HTML>

Description:

Ajax requests does not get aborted when using Chrome

Steps to reproduce the problem:

Load the test case and set up an appropriate URL
load the page

The result that was expected:

All ajax requests must be aborted
Screen from FF with Firebug:
Capture7.jpg

The result that occurs instead:

None of the requests was aborted
Capture8.jpg

Test Case:

Code:

      var req = Ext.Ajax.request({
                    url: './test/ajaxabort',

                    success: function(response){
                        console.log('success',response);
                    },
                    failure: function (response){
                        console.log('failure',response);
                    }
                });
                Ext.Ajax.abort(req);
                req = Ext.Ajax.request({
                    url: './test/ajaxabort',

                    success: function(response){
                        console.log('success',response);
                    },
                    failure: function (response){
                        console.log('failure',response);
                    }
                });
                Ext.Ajax.abort(req);
                req = Ext.Ajax.request({
                    url: './test/ajaxabort',

                    success: function(response){
                        console.log('success',response);
                    },
                    failure: function (response){
                        console.log('failure',response);
                    }
                });
                Ext.Ajax.abort(req);
                req = Ext.Ajax.request({
                    url: './test/ajaxabort',

                    success: function(response){
                        console.log('success',response);
                    },
                    failure: function (response){
                        console.log('failure',response);
                    }
                });
                Ext.Ajax.abort(req);
                req = Ext.Ajax.request({
                    url: './test/ajaxabort',

                    success: function(response){
                        console.log('success',response);
                    },
                    failure: function (response){
                        console.log('failure',response);
                    }
                });
                Ext.Ajax.abort(req);

HELPFUL INFORMATION Possible fix:

I traced it back and it seems that the method isLoading in Ext.data.Connection returns false because the state = 0....weird... :

Code:

isLoading : function(request) {         if (!request) { 

            request = this.getLatest(); 
        } 
        if (!(request && request.xhr)) { 

            return false; 
        } 
         
        var state = request.xhr.readyState; 
        return !(state === 0 || state == 4); 
    },

Additional CSS used:

only default ext-all.css

Operating System:

Win7

**mitchellsimoens** · 7 May 2012 12:49 PM

This is what I get in Chrome 18:

Screen Shot 2012-05-07 at 1.48.22 PM.png

All requests have been canceled (aborted). In FF12 they show aborted and the failure callback is fired just like in Chrome 18. Am I missing something?

**anton.dimitrov** · 7 May 2012 2:35 PM

Could you please provide me with your test case. Based my test case none of the requests get aborted(in Chrome) , the result is returned from the server, with the data and the success is fired.
Capture9.PNG

**mitchellsimoens** · 7 May 2012 2:38 PM

Originally Posted by anton.dimitrov

Could you please provide me with your test case. Based my test case none of the requests get aborted(in Chrome) , the result is returned from the server, with the data and the success is fired.
Attachment 34972

I used your code except I changed the urls to a local php script with a sleep(5)

**evant** · 7 May 2012 8:01 PM

In the same boat as Mitchell, I ran your test case, only changing the url to a local page, see the attached screen:abort.jpg

**anton.dimitrov** · 7 May 2012 11:37 PM

I found the issue and I am happy to say that it was with Chrome, my Chrome. I am migrating to 4.1 and it seems that the browser was still hanging to an old nightly build and not the latest one , which was causing the weird problem with the abort. Silly me..

10x for the help

Cheers

**mitchellsimoens** · 9 May 2012 5:26 AM

Originally Posted by anton.dimitrov

I found the issue and I am happy to say that it was with Chrome, my Chrome. I am migrating to 4.1 and it seems that the browser was still hanging to an old nightly build and not the latest one , which was causing the weird problem with the abort. Silly me..

10x for the help

Cheers

Anytime, glad it was resolved in one way or another!

[4.1.1 rc1] Ext.Ajax.abort() does not abort the request in Chrome

Thread Tools

Search Thread

Display

[4.1.1 rc1] Ext.Ajax.abort() does not abort the request in Chrome

[4.1.1 rc1] Ext.Ajax.abort() does not abort the request in Chrome

Tags for this Thread