conflicts of js libraries with Extjs

[GoogleCodeExporter]

What steps will reproduce the problem?

apparently a conflict between the js of managediframe and the own ones of extjs 
exists. In the application that we are developing we had the necessity to 
occupy the extension managediframe to create iframe. On the other hand, in the 
application that we are developing we have the necessity to eliminate the 
objects occupying the Ext.destroy method of the js Extjs, but when including 
the js of managediframe, apparently the method destroy of extjs does not work 
suitably. That is to say, apparently a conflict of js exists, if we eliminated 
js managediframe everything returns to normality. In order to realise the 
elimination of the objects we occupied the following code (file Annex), which 
works correctly without including js of managediframe, but when including it 
stops them working. 

These functions are used to eliminate the components and to release the memory 
space that these components in the navigator consume (mainly Internet to 
explorer). Since our application generates many components but framework extjs 
does not release the memory resources correctly and an almost exponential 
increase in the memory consumption is observed. 

What version of the product are you using? On what operating system?

The version that this taking care is ManagedIFrame (MIF 2,1) and Ext JS Library 
3.2.0, Internet explorer 7, winxp

Original issue reported on code.google.com by josue.no...@gmail.com on 16 Mar 2011 at 7:27

Attachments:

• myfunction.js

[GoogleCodeExporter]

Just confirming the bug, im using exactly the same configurations.

Original comment by vitor.leitebraga@gmail.com on 25 Jul 2011 at 8:11

[GoogleCodeExporter]

miframe.2.01 is compatible with 3.0.x only, then update it.

Original comment by rafaeldobau on 26 Jul 2011 at 1:50