I have a dashboard with 3 major components. HTML Document, iframe1 and iframe2. See the image below (iframe1 is hidden).

When the dashboard initially runs, the summary page is visible. Selecting any other button, hides iframe2 and exposes iframe1. This works great accept the controls under the buttons are blocked.

If I use tasks and animations to toggle the iframes, it works perfectly but, it toggles on and off the iframes and you end up with wack-a-mole. When I manage visibility with JavaScript, iframe2 appears hidden, but blocks the controls under the buttons.

Any help with this would be greatly appreciated. Thank you,

Summary View (iframe2)


All other views (buttons) (iframe1)


JavaScript that controls iframe visibility;

 // iFrame visability
if (CN.indexOf("button") > -1) {
    if (v14 == 'iframe1') {
//        IbComposer_showHtmlElement("iframe1", true);
document.getElementById("iframe1").style.visibility = "visible";
document.getElementById("iframe2").style.visibility = "hidden";
//                IbComposer_showHtmlElement("iframe2", false);
     }
    else
    {
//        IbComposer_showHtmlElement("iframe1", false);
//        IbComposer_showHtmlElement("iframe2", true);
document.getElementById("iframe1").style.visibility = "hidden";
document.getElementById("iframe2").style.visibility = "visible";
    }
} 

This message has been edited. Last edited by: Don Garland,

Hi Don,

May not be the same reason since you seems to use WF8.09 but I had a similar issue where when I swap from one tab (page) to another I was not able to access (click) on the controls.

I was under WF8201M gen 193 and upgrading to gen 240 solve the issue. Maybe you should look if another gen (or upgrade) is available to you.

But it may be something totally different and a simplest solution may exist.

Thanks Martin, its just odd that it works using Tasks & Animation.

Hey Don,

Do you get the same results in Chrome and IE?

I had similar issues as Martin stated: "I was under WF8201M gen 193 and upgrading to gen 240 solve the issue." while in 8202M Gen 16. and needed to go to 8202M Gen 60 to alleviate the issue.

No, it works in Chrome

This message has been edited. Last edited by: Don Garland,

CSS visibility does not remove an element from view, it just makes it invisible. It's still there, blocking everything behind it. That has it's uses, but this isn't one of them.

What you're looking for is display = "none" and display = "block" respectively.

quote:

What you're looking for is display = "none" and display = "block" respectively.

The following works perfectly. THANK YOU!

 // iFrame visability
if (CN.indexOf("button") > -1) {
    if (v14 == 'iframe1') {
        //IbComposer_showHtmlElement("iframe1", true);
document.getElementById("iframe1").style.display="initial";
        //IbComposer_showHtmlElement("iframe2", false);
document.getElementById("iframe2").style.display="none";
     }
    else
    {
        //IbComposer_showHtmlElement("iframe1", false);
document.getElementById("iframe1").style.display="none";
        //IbComposer_showHtmlElement("iframe2", true);
document.getElementById("iframe2").style.display="initial";
    }
}