getFrameDocument not working for IE in Quirks mode?
Hi Doug,
Thanks for all your hard work! I took a look at the 2.1.5 version of getFrameDocument(), and it looks like this:
Code:
getFrameDocument : function() {
var win = this.getWindow(), doc = null;
try {
doc = (Ext.isIE && win ? win.document : null)
|| this.dom.contentDocument
|| window.frames[this.dom.name].document || null;
} catch (gdEx) {
ELD.clearDocumentCache && ELD.clearDocumentCache(this.id);
return false; // signifies probable access restriction
}
doc = (doc && Ext.isFunction(ELD.getDocument)) ? ELD.getDocument(doc,true) : doc;
return doc;
}
The alpha2 version is this:
Code:
getFrameDocument : function(assertAccess) {
var win = this.getWindow(), doc = null;
try {
doc = win.contentDocument || this.dom.contentDocument || window.frames[this.dom.name].document || win.document;
} catch (gdEx) {
doc = false; // signifies probable access restriction
}
return Ext.isDocument(doc, assertAccess !== false) ? doc : false;
}
It looks like the Ext.isIE shortcut in the 2.1.5 version is removed from the alpha2 version, and I believe this is causing issues with running in IE in Quirks mode.
What is happening for me is that the parent document, not the iframes document, is being returned from the
Code:
window.frames[this.dom.name].document
call. The property has the correct reference to the iframe document, but in the alpha2 code, that code isn't reached.
Is this an intentional decision that you made?
Cheers,
Nicholas
ManagedIFrame and ExtJS 4.1 RC3?
Does this MIF work with the ExtJS 4.1 RC3?
MI A2 throws error with Extjs 4.1 final release
Hi,
we are getting error as (a.replace is not a function), when try to use the MI A2 with Extjs 4.1 final release.
Please let us know when we could get the latest version of MI, which could work with Extjs 4.1 code line.
Thanks in advance.
Regards,
Soosai