Hi - In response to your latest thread:

- Our VWG Version = VWG_Professional_Studio_6.4.0_Release_JQT_Beta3_NET4.0
- We reviewed your sample application - quite different (more simplistic) than our production situation
   In your sample application:
   - You are not using your recommended DocType =  <! DOCTYPE html PUBLIC "-//W3C//DTD html 4.0 Transitional//EN">
   - Our 1st Host page is on Ning, our 2nd iFrame host is .aspx (both your host pages are .html)
   - Due to our ASP.Net host : We use .ashx (not .vwg) 
   - We pass URL parms
   - For Example: We use : post.Home.ashx?nID=xxx
   - If we turn IE Compatibility on, then IE works, otherwise VWG fails, and IE displays blank iFrame

Hopefully this detailed info above can help solve this iFrame issue

 Hi Soft-Designs,

Thanks for the additional info. I don't think using .ashx as extension has any effect here and I doubt that me using html and you using aspx would make any difference, but still, you never know. The different and non-recommended DOCTYPE I placed in the Html files were placed there for a purpose and I was hoping you would modify the application and upload it so I could reproduce. 

I do however think that  you and James have both hit the nail directly on the head here (thanks James) and the reason for me not seeing anything wrong was because of my IE9 jumped into Compatibility mode for whatever reason. As you mention yourself, turning on IE compatibility mode makes the Visual WebGui application work correctly. When making sure IE9 is not in compatibility mode, I can see the problem (finally). 

Googling a bit on this problem, it seems that it is an IE(9) problem with IFrames, where IE9 forces the child IFrames to have the same doctype as the parent. You can see this thread here for instance. Acting on the recommended, or more precisely the only, workaround available for us generally I placed the following meta in the head section of the Html file (see description below):

<meta http-equiv="X-UA-Compatible" content="IE=8" />

If you place the above meta inside HtmlPage1.htm, the Form1 works (tested on 6.4.0 Release Beta3 JQT and also on upcoming WinWeb 6.4.0 Release e).

If you place the above meta only inside HtmlPage2.htm and not in HtmlPage1.htm, it doesn't work.

Please check if you can use this information to modify your Html (aspx) pages to include this meta tag and see if you can work around the problem that way. It doesn't seem that we have a whole lot of options for IE9 at the moment.

P.S. In association with our upcoming Enterprize Mobile framework (due end of Q2) a new DOCTYPE will be introduced in Visual WebGui application. Could be that it will fix this incompatibility with IE9 and IFrames, I just can't fully confirm yet.

Hope this helps,

Palli