View Full Version : ExtJS and Internet Explorer 6 !

10 Apr 2013, 2:02 AM
Lot of official examples does NOT work in Internet Explorer 6, some of them say that there is no xmlhttprequest defined, so I assume there is no support for IE 6 in ExtJs , right ?

10 Apr 2013, 2:16 AM
Unfortunately, we do support IE6 and it's part of our testing. Where are you seeing problems?

10 Apr 2013, 2:28 AM

we face this problem when we even try to open the examples page for ExtJS 4.x from IE6. Also even if you open the www.sencha.com site with IE6 you get plenty of errors.

10 Apr 2013, 2:41 AM
check activex is activated...

10 Apr 2013, 2:55 AM
It is activated. This is the first error we get in www.sencha.com. In our application we have more, but it does not make any sense to investigate them now, since even the site does not work.


10 Apr 2013, 5:10 AM
I have same errors !

11 Apr 2013, 4:48 AM
so it there any solution for this problem ???

11 Apr 2013, 5:19 AM
Seems like something is busted on our website, it shouldn't affect the stuff in the framework.

11 Apr 2013, 5:34 AM
IE6 on my application is not running anymore. Well its running...but incredibly slow..and buggy

11 Apr 2013, 5:48 AM
None of the official examples are working for me, and I am getting such errors that I believe it will NOT work even in IE7

11 Apr 2013, 7:53 AM
I'm also very interested in the IE6 compatibility and can confirm that with the official IE6 test machine of Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=11575) neither the sencha homepage nor the examples or the extjs documentation is working in IE6.

Can we expect this being fixed in an upcoming patch or version? Otherwise I might probably need to search for an alternative to extjs.

11 Apr 2013, 9:04 AM
Can we expect this being fixed in an upcoming patch or version? Otherwise I might probably need to search for an alternative to extjs.

Also for us, this compatibility with IE6 was the main reason for choosing ExtJS

12 Apr 2013, 12:30 AM
Can somebody answer if there will be fix for internet explorer in future?

15 Apr 2013, 9:01 AM
Is there any official response/reply/thoughts on this issue? It is becoming really urgent for us to find a solution...

16 Apr 2013, 6:57 AM

16 Apr 2013, 7:57 AM
The thread is now one week old and no official response beside:

Unfortunately, we do support IE6 and it's part of our testing. Where are you seeing problems?

What are these test you claim to have performed?
As already complained and confirmed by others, neither the official examples nor the documentation are currently working in IE6.

I'm a little bit upset that there is no real statement of sencha up until now.
The features of your product does not comply with the ones you are advertising with!
In a more rigorous way of thinking the facts above together with the absence of any reaction from your side could be interpreted as a fraud.

Just as a reminder.... a small quote from your ExtJS product description (http://www.sencha.com/products/extjs/):

Ext JS 4 makes it easy to build an app that gives you the power of the web regardless of what browser your customer uses.

Ext JS supports all major web browsers including:

Internet Explorer 6+
Firefox 3.6+ (PC, Mac)
Safari 4+
Chrome 10+
Opera 11+ (PC, Mac)

Sencha Team, please provide a proper statement to this question as soon as possible.

16 Apr 2013, 8:40 AM
I just pulled up the examples page from sencha.com and opened the Kitchen Sink demo on an XP machine running IE6 and was able to run the panels, grid, tree, and tabpanel examples under Classic and Neptune themes without issue.

What issues are you seeing?

16 Apr 2013, 1:26 PM
As I said above, we test the framework in IE6, here's it is running one of them:


17 Apr 2013, 1:41 AM

h (http://www.screencast.com/users/Alexdav89/playlists/senchaie6)ere are error screenshots, it is weird why IE6 works differently for us, you have installed some plugin to force IE6 work for you or something like that?

19 Apr 2013, 1:22 AM
Nobody knows what are the errors on my screenshots?
I am waiting for reply more than 2 days already.

19 Apr 2013, 1:30 AM
XMLHttp Requests for IE6 are activex objects, so somewhere in your browser that activex obejct is not available.

var xmlhttp;
if (window.XMLHttpRequest)
{// code for IE7+, Firefox, Chrome, Opera, Safari
xmlhttp=new XMLHttpRequest();
{// code for IE6, IE5
xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");

19 Apr 2013, 1:51 AM
I know , I have done this 1000 times when I write Ajax manually, but in this case we use Extjs framework and this must be done by framework.
I have not created XMLHttpRequest object myself in application that is what extjs does internally and it MUST be fixed by framework developers itself it can not be fixed in my application.

19 Apr 2013, 1:59 AM
Its I think in the Ext.data.Connection

getXhrInstance: (function() {
var options = [function() {
return new XMLHttpRequest();
}, function() {
return new ActiveXObject('MSXML2.XMLHTTP.3.0');
}, function() {
return new ActiveXObject('MSXML2.XMLHTTP');
}, function() {
return new ActiveXObject('Microsoft.XMLHTTP');
}], i = 0,
len = options.length,

for (; i < len; ++i) {
try {
xhr = options[i];
} catch(e) {
return xhr;

Anyway the try catch is, I think, raising questions by itself. You could try to override this function .

19 Apr 2013, 2:23 AM
Firstly the error screenshots are from official examples.
And secondly I expect from framework to work in IE6 as it is written on official site, without overrides or hacking into framework code.

19 Apr 2013, 2:50 AM
Of course, for that reason it is good to know what part in the function is giving the error. By overriding it and set some console logs or alerts you could debug that. To be sure that the error is not caused by your browser configuration settings. Seeing the answers Sencha gives, the samples work for them.

Only thing I can see in your case is that activex is not available or is throwing an exception on creating an instance. The raison why is I think captured in that try catch part.

19 Apr 2013, 10:47 AM
I am seeing the issue you're seeing on the docs page and I can raise that issue internally. But, the examples pages running the code itself seem to be ok. Are you having trouble if you visit the examples pages as well?

21 Apr 2013, 6:17 AM
yes, example demos on website look fine, but there are errors in documentation examples and also in architect generated code.

21 Apr 2013, 6:32 AM
I was wondering what the reason is that you need IE6 support to begin with. According to http://www.ie6countdown.com/ , less than 7% of the entire world uses IE6, and the majority of the users are located in China. Are you developing an application for Chinese users, or do you have a business requirement that it must support IE6?

If you must code with IE6 support, does that also mean that the computers your users will be using are severely underpowered compared to today's computers? ExtJS is great, but if you care about performance, you're probably not going to have the best of luck with old versions of IE, especially when paired with legacy machines.

21 Apr 2013, 9:12 AM
I agree with krullj. The moment Google dropped support for IE6 so did I. IE6 has bunch of vulnerabilities and it is no longer (for quite some time) supported by Microsoft itself.