Here is the error message upon installation. 

Understood.  Thanks for your reply.  Ultimately the best scenario is likely to open a new browser window on top of the WebDesktop with the navigation toolbars hidden.

Thank you, gentlemen.

Hello,

No I do not experience the performance problem  if I don't use WebPaneManager.  The problem clearly lies with me using nested IFrames within a WebPane.

Please do the following to reproduce this issue:

 - Create a page Default.aspx that contains a WebPaneManager and 1 pane, and loads Pane.aspx

- Create a MasterPage named MasterTab1.aspx that contains a WebTab control.

- Create a MasterPage named MasterTab2.aspx that contains a WebTab control

- Create a page Pane.aspx that uses masterpage layout MasterTab1.aspx

- Create a page Subtab.aspx that uses masterpage layout MasterTab2.aspx

- Dynamically create a WebTabItem in Pane.aspx that loads SubTab.aspx

- Dynamically create a WebTabItem in SubTab.aspx that loads Content.aspx (any static content)

----------------------------

Doing the above should replicate my problem.  The problem lies in creating multiple nested IFrame windows within a WebPane.  I'm not sure if the master page is contributing to this issue.

As I explained in my support ticket, I'll be happy to supply more code directly to a technician but not post it publicly.

I also have a live dev site that I can share with you to replicate the issue.

Alex

Thank you for your reply.

My code is nearly identical to yours.  Instead of getting the instance of WebDesktopManager1 from the WebDesktopWindow using your code below....

        function Button1_onclick() {
            var desktop = window.parent.ISGetObject("WebDesktopManager1");
            var window2 = desktop.CreateWindow();
            window2.Text = "Window2";
            window2.Name = "Window2";
            window2.ContentURL = "http://google.com";
            window2.ContentMode = "UseIFrame";
            window2.AllowMinimize = "No";

            desktop.Windows.Add(window2);
            window2.Show();
        }

I call  parent.addWindow() which calls my own javascript function on the same page.  This prevents me from having to add a javscript function on each WebDesktopWindow page that will need to open a new window.

My method:

    function addWindow(name, text, imageURL, contentURL, width, height, allowMin, allowMax, allowClose, isMaximized, focusIfExists )
    {
        var dm = ISGetObject("WebDesktopManager1");
        var wnd = dm.GetWindow(name);
        if (wnd == null || focusIfExists == 'False')
        {
            wnd = new WebDesktopWindow();
            wnd.Text = text;
            wnd.Name = name;
            wnd.ControlBoxImage = "is_webdesktop-16.gif";
            wnd.ContentURL = contentURL;
            wnd.ContentMode = "UseIFrame";
            wnd.AllowMinimize = allowMin;
            wnd.AllowMaximize = allowMax;
            wnd.AllowClose = allowClose;            
            dm.Windows.Add(wnd);
            
            wnd.ResizeTo(width, height);

            if (isMaximized == 'True')
            {
                wnd.Maximize();
            }
            wnd.Show();
        }
        else
        {
            wnd.Activate();
            wnd.Show();
        }
    
    }

In either case, I am experience performance issues in Internet Explorer.

I SHOULD ADD, Internet Explorer also has poor performance when simply clicking on the Close icon (x) in the corner of each WebDesktopWindow.   It's not a horrible delay -- but takes nearly 1 full second to close the window.  Firefox does not have these performance issues.... and I don't have this delay when accessing the Developer Network UI.

Thank you in advance for any suggestions that you may have.

This issue has been resolved.

Problem was due to CSS formatting that impacted the WebCombo control