How do I force a refresh of the embedded IFRAME once I've set the ContentUrl parameter? I've set ContentUrl on the client side using the method you describe and then call oDialog.show() but the IFRAME does not display the newly updated ContentUrl.

Thanks...

 Ya..that kind of annoys me as well.  I will see about getting that fixed in a future release.

 Glad you got it working.

Devin

Devin Rader"]Are you setting a contenturl on the server in the controls markup (or in code when the page is initially rendered).

The Answer was No, now it is Yes and it is working like a charm.  Thanks alot! that was driving me crazy.

Patrick

Are you setting a contenturl on the server in the controls markup (or in code when the page is initially rendered).  I know there is an issue where, if the control does not have a contenturl set on it when it initially renders, the iframe it uses to display the contenturl never actually gets rendered since the dialog window thinks you are just using its template.

Can you try to get a handle on the iframe using the code I provided earlier in this thread to see if the iframe is even there?  Alternatively you could use something like the IE Web Developers Toolbar to examine the live DOM to see if the iframe is there.

I think this is something we will try to fix in a future version, giving you some way to force the control to render its iframe, even if you do not initially give it a content URL.  If you discoiver this is your issue, then the workaround is simply to set a contenturl on the control during the initial page load to the iframe gets rendered.

Devin

Hello -

I am running into a very similar if not the same problem... 

In IE6 I am trying to use the webdialogbox to display information related to a row in a datagrid by using another aspx page to handle the data processing and display and then display the aspx page in the wdb.

The problem I am running into is that the page is never displayed in the web dialog box. Also, I am not receiving any client side script errors. I am using the client side event for cell click on the uwg. The wdb was created at design time.

BLOCKED SCRIPT

//Capture mouse event and location

//alert(cellId);

var cellCol = cell.Column;

var cellRow = cell.getRow();

var x = document.form1.htmltxt_X.value;

//alert("x: " + x);

//alert("y: " + y);

dialog.set_top(y+'px');

//var myIframe = dialog.get_contentPane().get_element().getElementsByTagName("ModHistroyFrame")[0];

//myIframe.contentWindow.location.href = "http://Discovery/dotnetprogramsdev/efc/Opp_Mod_History.aspx?OppID=" + rowDataKey

 Hello Manuel,

I discovered something similar to what you report in another forum thread:

http://forums.infragistics.com/forums/p/5675/25206.aspx#25206 

This appears to be a FireFox only issue and the current workaround is the following:

        var iframe = oWnd.get_contentPane().get_element().getElementsByTagName("IFRAME")[0];                      
            iframe.contentWindow.location.href = "http://es.infragistics.com";    

I will be logging this as a bug in our bug tracking system and hopefully a fix for that will be available very soon.

Please, excuse us for the inconvenienice.