Iframe page loading is asynchronous. So, use the listeners : { } to wait for the dataavailable event to fire, THEN interact with the frame document (see the example page included in the zip for other samples)

2) Is there any performance issue of loading each page in ManagedIframe?

Yes, IFRAMEs are expensive to operate. Use them to isolate CSS/bad behavior from your parent page. There are good reasons to use them (adWare, media, PDFs, mashups/portals, legacy App migration, etc), but they do take their toll.

3) Is there any document that I can reference other than looking at code ?

My signature block below has links the documentation site and FAQ for the previous release. As this is still an Alpha release, there is not yet official docs for this version yet. There are several new feature but the MIF.Element methods are largely the same.

Study the zip-enclosed mif.js example closely. Much can be garnered from that.

Iframe page loading is asynchronous. So, use the listeners : { } to wait for the dataavailable event to fire, THEN interact with the frame document (see the example page included in the zip for other samples)

2) Is there any performance issue of loading each page in ManagedIframe?

Yes, IFRAMEs are expensive to operate. Use them to isolate CSS/bad behavior from your parent page. There are good reasons to use them (adWare, media, PDFs, mashups/portals, legacy App migration, etc), but they do take their toll.

3) Is there any document that I can reference other than looking at code ?

My signature block below has links the documentation site and FAQ for the previous release. As this is still an Alpha release, there is not yet official docs for this version yet. There are several new feature but the MIF.Element methods are largely the same.

Study the zip-enclosed mif.js example closely. Much can be garnered from that.

I have just upgraded the ext to 4.1 and seems to have some issue with multidom.js
I will take a look as well where the problem is.. if you see the problem, can you let me know ??

@rkim --

MIF 4.0/multidom is NOT compatible with 4.1.anything.

That said, MIF 4.1 is undergoing testing under the 4.1-beta (as the internals have changed considerably in that release). If you are not using Ext.core.Element methods to query/manipulate IFRAME documents you can probably continue to use the 4.0 version of the MIF component only -- until MIF 4.1 is released....

That said, MIF 4.1 is undergoing testing under the 4.1-beta (as the internals have changed considerably in that release). If you are not using Ext.core.Element methods to query/manipulate IFRAME documents you can probably continue to use the 4.0 version of the MIF component only -- until MIF 4.1 is released....

Resizable panel is having issues when including the multidom.js

Receiving the error "dom.getBoundingClientRect is not a function" (ext-all-debug.js line 8849) when trying to re-size a panel and the javascript file multidom.js is included. The resizing works fine when the multidom.js is NOT included. I am using ext-js 4.0.7. Is this a known issue? Any other ideas?

Attached is a zip file containing an html file which can be dropped into the ext-js examples folder. The panel is resizable on the south border. With the multidom.js included in the html then the resizing does not work. Remove the multidom.js and the resizing will work.