On Mozilla MDM, about XmlHTTPRequest, you can read:
Note: You may not use a timeout for synchronous requests with an owning window.
So a better work around could probably be to change the line (1009 in v4.0)
toCode:if(callback && callback.timeout){
Code:if(callback && callback.timeout && options.async){
in ext-basex.js 4.1 about line 1011
('timeout' in r) && (r.timeout = callback.timeout);
modified to :
(options.async) && ('timeout' in r) && (r.timeout = callback.timeout);
Nice digging guys! ;)Quote:
Originally Posted by hairinwind
I'll include this on the next build.
I'm working on a desktop app with extjs 3.2 (using basex for local file system access) and I'm having problems in IE9: when I reload repeatedly the page it crashes, this wasn't happening with IE8 and I haven't change my code. So, I believe that I have some sort of compatibility problem going on, I already tried to migrate to 3.4 (I would like to go foward with 4.x but I don't have the plugin to run my app locally yet... hope it will be soon). The problem is that with 3.4 I started to have issues with basex, when reloading the app doesn't crash but there's a lot of error messages from basex.
So the thing is, there's going to be another version of ext-basex adding compatibility with ie9? There's going to be/is something on extjs4.x to prevent from using this plugin and be able to run an app locally, without a webserver?
Thanks in advanced.