[2.0 only] ux.ManagedIframe/Panel (1.2.7)

[hendricd]

Can you post a current MIF and surrounding panel configs. Something doesn't sound right (just can't see it yet)

[cmarin]

Really appreciate this. Is this enough code or would more be better? Also, is there any way to make it so that Visual tab can't be closed?

    new Ext.TabPanel({
    region:'center',
    id:'tabPanel',
    deferredRender:false,
    activeTab:0,
    items:[{
        contentEl:'extform',
        title: 'Form',
        autoScroll:true
    },{
        title: 'Visual',
        id         : 'visual_tab',
        xtype     :'iframepanel',
        frameConfig: { name : 'vizwin' }
    }]
})
         ]
    });
    Ext.getCmp('visual_tab').setSrc('/cms/content/visual_edit?id=1&zone_id=1'); 

Can you post a current MIF and surrounding panel configs. Something doesn't sound right (just can't see it yet)

[hendricd]

Also, is there any way to make it so that Visual tab can't be closed?

Add closable:false to each tabPanel item.

Not much help with the last post. The viewport is going to consume the entire browser client area, so content smaller than its borders (by default) will not generate scroll bars unless overflow occurs.

Do scrollers appear if you resize the browser (making it smaller)?
Do you have a live URL running to look at somewhere?

[svdb]

@svdb -- The MIF.setSrc function is wrapped for exception event handling, so IE6 must not be raising one for a mangled URL.

Are you suggesting validation before applying it?

In fact no. I can live w/o validation. On FF i'm using the exception notification to display a user friendly message-mask over the mif when a 404 is returned. Somehow the 404 causes a MIF exception to be raised, and that's exactly what I need. So, this works on FF, but not on IE: no MIF exception gets raised on IE.

So my question in fact was, do you think this is because IE catches the 404 and replaces it by it's own default msg page before the iframe (and mif) gets a chance to notice there even was a 404, and there's nothing we can do about it?

[hendricd]

@svdb -- MIF doesn't trap HTTP status on the frame It can't, unless you are using MIF.update (UpdateManager); then you could.

[colinexl]

Hi All,

I'm putting and iframepanel inside a Panel which is inside a Window. I want the window with the iframe to show only after a button has clicked.

Here's the code for the Window:

Ext.onReady(function()
{            
    createSetupChannelWindow = function()
    {
        dialog = new Ext.Window(
        {
            title: 'Add New User',
            autoScroll: true,
            modal: true,
            closable: false,
            maximizable: false,
            layout: 'fit',
            listeners:
            {
            //close: function(p) { setTimeout('app.users.reload()', 1000); }
            },
            items:
            {
                layout: 'card',
                xtype: 'panel',
                id: 'iFrameContainer',
                defaultType: 'iframecontent',
                autoScroll: false,
                items: 
                [{
                    xtype: 'iframepanel',
                    id: 'iFrameContent',
                    loadMask: true,
                    autoShow: true,
                    layout: 'fit',
                    defaultSrc: 'channelAdd'
                }]
            }
        });
        dialog.show();
        dialog.setSize(800, 400);
        dialog.center();
       } 

my Iframe is just a simple HTML page, for example "http://ww.google.com".

In Firefox and IE, when I click on the button that displays the Window with the iframe, I see the window but no content in the iframe.

I inspected the DOM and I noticed that the problem is my iFrameContent DIV has a class "x-panel x-hide-noresize" in Firefox. In IE I get a "x-panel x-hide-display".

I tried doing

Ext.get('iFrameContent').setVisible(true) 

It works in FF, but in IE I'm still getting "x-panel x-hide-display" so nothing is displayed in IE.

I was wondering why I'm getting this behavior, why is my iframe set to "hidden" on default?

Thanks,
Colin

[hendricd]

@colinexl -- the x-hide-nosize is designed to solve the iframe/object/embed reflow problem (outlined here). As your layout involves a heavily nested heirarchy, start out by "living with the problem" to get the basics working. For now, add this in:

items: 
     { 
       layout: 'card', 
       xtype: 'panel', 
       id: 'iFrameContainer', 
       defaultType: 'iframepanelcontent', ??
       defaults : {  hideMode : 'display' },
       autoScroll: false, 
           items:  
           [{ 
                xtype: 'iframepanel', 
                id: 'iFrameContent', 
                loadMask: true, 
                autoShow: true, 
                layout: 'fit',  //iframe panels have no items
                defaultSrc: 'channelAdd' 
              }]
.... 

Later, if you care whether your frame(s) refresh when you least expect it, you'll have to apply similar fixes in your upstream containers. I have a plugin (for any Ext.Component) I'll be releasing shortly to make that easier for all.

[hendricd]

@colinexl -- just tried your example. The reason why the panels (cards) are hidden is because they are not visible in a card layout until you have an activeItem:

items: 
     { 
       layout: 'card', 
       xtype: 'panel', 
       id: 'iFrameContainer', 
       defaultType: 'iframepanel',
       activeItem : 'iFrameContent',
       autoScroll: false, 
           items:  
           [{ 
                xtype: 'iframepanel', 
                id: 'iFrameContent', 
                loadMask: true, 
                autoShow: true, 
                layout: 'fit',  //iframe panels have no items
                defaultSrc: 'channelAdd' 
              }]
.... 

[colinexl]

@Doug Hendricks

Hi Doug,

Thank you very much for the reply. The problem was like you said, I didn't have an "activeTab" config option. Adding it in solved the problem!

However, I still have a problem with the loadMask in IE7. In FF it works fine, but in IE I get a "false" text instead of a load mask.

I've attached two screen shots to show this error.

Thanks,
Colin

[hendricd]

@stever -- Sorry, browsers will not permit an embedded script tag with a src property unless the iframe itself has a src property referencing a valid URL.

That used to be the common iframe-injection tactic. That door is now closed.