I've got the same problem in f***ing IE, and found the following Workaround:
The line throwing the runtime error is the following:
Code:
el.innerHTML = createHtml(o);
(line 412 in ext-all-debug.js (ext-3.1.1)
IE always crashes here, no matter which value is assigned to innerHTML property.
This doesn't happen if innerHTML property is not empty.
So I created the new Ext.Element based on an existing HTML Element:
HTML Code:
<div id="iesucks"></div>
Code:
var el=new Ext.Element(Ext.get('iesucks'));
//do something with the el...
// clear the html element to avoid changes from displaying in it...
calframe2.update('');
Hope this helps until IE hopefully will be forbidden by law, or this issue is fixed...