[3.0.x, 3.1.1] ux.ManagedIFrame 2.x

[hendricd]

@dubrovsky -- The only way to trap a catastrophic server failure like that (and using an iframe to host the page) is with an Ajax call to populate the frame with the server's entire page response. In other words, use autoLoad instead of defaultSrc.

Then you have trappable control over the server failure:

var tab = tabpanel.add({
            xtype:'iframepanel'
            ,title: 'CIM/SMGS'
            ,closable: true
            ,cls:'x-panel-body'
            ,loadMask:{msg:"Loading..."}
            ,autoLoad: {
                   url      : 'Smgs_create.do',
                   params: { task : 'create' },
                   scripts : true,
                   method : 'GET',
                  callback : function(el, success, response, options){
                          //sent back HTTP status 50x?
                          if(!success){  return complain( response.status ); } 
                  }
          });

However, the trade-off is you'll likely need to use absolute URL's in your child page's script/link tags.

[dubrovsky]

@dubrovsky -- The only way to trap a catastrophic server failure like that (and using an iframe to host the page) is with an Ajax call to populate the frame with the server's entire page response. In other words, use autoLoad instead of defaultSrc.

Then you have trappable control over the server failure:

var tab = tabpanel.add({
            xtype:'iframepanel'
            ,title: 'CIM/SMGS'
            ,closable: true
            ,cls:'x-panel-body'
            ,loadMask:{msg:"Loading..."}
            ,autoLoad: {
                   url      : 'Smgs_create.do',
                   params: { task : 'create' },
                   scripts : true,
                   method : 'GET',
                  callback : function(el, success, response, options){
                          //sent back HTTP status 50x?
                          if(!success){  return complain( response.status ); } 
                  }
          });

However, the trade-off is you'll likely need to use absolute URL's in your child page's script/link tags.

I've followed your advise and use this code block and absolute URL's in my child page's script/link tags(I also tried to use relative url's - it's all the same). In Firefox 3 everything works perfectly, but in IE6 i've got the error - "Ext is undefined". Could you help me, please, how to avoid this IE6 pitfall.

[zombeerose]

What would be the recommended way to set some markup within a MIF? Basically, I want to apply a CSS style sheet to the source page that is loaded in the frame.

Thanks!

[hendricd]

What would be the recommended way to set some markup within a MIF? Basically, I want to apply a CSS style sheet to the source page that is loaded in the frame.

Thanks!

@zombeerose --
If your css demands are minimal:

var nestedRules = [
   'x-hidden{visibility:hidden;}',
   'x-hide-display{display:none;}' ].join(' ');

MIFP.on('domready', function(frame){
     frame.CSS.createStyleSheet( nestedRules );

});

If not,

 MIFP.on('domready', function(frame){
     var D = frame.getFrameDocument(),
          head = D ? D.getElementsByTagName("head")[0] : null; 
     if(D && head){
         Ext.DomHelper.append(head, {
             tag  : 'link',
             type: 'text/css',
             rel   : "stylesheet" ,
             href="http:/example.com/css/yourRules.css"  //absolute address likely required
        });
    }
 });

[zombeerose]

Thanks hendricd! I was hoping for a "fancier" solution but that worked.

[cherbert]

My application uses the little pop down message boxes used in many of the Ext sample pages...

Ext.example.msg....

My application errors whenever I try and call Ext.examples.msg with the ManagedIFrame2 (RC2) installed.

el.style is undefined
if(v = el.style[prop]){\r\n       mutidom.js (Line 591)

My includes are....

<script type="text/javascript" src="./js/miframe/multidom.js"></script>
<script type="text/javascript" src="./js/miframe/mif.js"></script>

[hendricd]

My application uses the little pop down message boxes used in many of the Ext sample pages...

Ext.example.msg....

My application errors whenever I try and call Ext.examples.msg with the ManagedIFrame2 (RC2) installed.

el.style is undefined
if(v = el.style[prop]){\r\n       mutidom.js (Line 591)

My includes are....

<script type="text/javascript" src="./js/miframe/multidom.js"></script>
<script type="text/javascript" src="./js/miframe/mif.js"></script>

Hmm, @cherbert. I'll take a look at that a bit closer. Pls stand by...

Just curious, is 'el' (or, this.dom) a document in the debugger for you when it fails there?

[cherbert]

Sorry it doesn't really give me much more apart from the error being on line 591 of multidom.js.

But the above error triggers everytime I try to use Ext.example.msg(...

The application then halts.

[decker.net]

Hi, miframe RC2 doesn't work when I use it with extjs + jquery-adapter from ext 3.0 distribution. It seems that Ext.lib.Dom class doesn't have several methods, such as "getDocumentHeight", "getDocumentWidth" and other. Miframe fails when it try to overload non existing methods. With ext-base adapter miframe work fine.

[hendricd]

Sorry it doesn't really give me much more apart from the error being on line 591 of multidom.js.

But the above error triggers everytime I try to use Ext.example.msg(...

The application then halts.

Hi, miframe RC2 doesn't work when I use it with extjs + jquery-adapter from ext 3.0 distribution. It seems that Ext.lib.Dom class doesn't have several methods, such as "getDocumentHeight", "getDocumentWidth" and other. Miframe fails when it try to overload non existing methods. With ext-base adapter miframe work fine.

@cherbert, decker.net -- Give the latest kit from SVN (or RC2-1.zip on first post) a try. It should resolve both issues.