I have attached two images to this post. They are screenshots of Chrome vs Opera for the code mentioned above. The window that I am showing in the screenshots opens up smaller than anticipated in Opera. Other RadWindows I have open larger than anticipated.

I did some searching on the Telerik forums, and found this link from 2009. I am not sure if this discussion is still applicable current day, however. If so, does Telerik have any suggestions on best practice for handling this scenario?

The first thing I notice is that your setting your RadWindow height to 100, which in another post I've read here says that the RadWindow's iFrame cannot be set below 125 as it's a browser limitation of the iFrame itself.

Have you tried setting it to a larger height and seeing it makes a difference?

Ahh, you know what, you're correct. In speaking with Telerik I did, in fact, learn this -- it seems that perhaps Opera works a bit differently and isn't 'forced' to hold an iframe smaller than 150px.

So, here's what I've got to report now:

If I set the window discussed previously to a height of 150px the INITIAL height of the window looks correct. BUT, if I open the window a second time it sizes improperly and becomes too small. BUT, if I remove "ReloadOnShow = false", and force it to reload every time, it sizes properly every time. This is not a big deal to me as I think I'm going to be reworking the window (today?).

How about for this window? It is sizing too large -- I suspect the same fix could be applied to all the windows which size too large.

Marin Bratanov

On the link to the old forum post - yes, this is still valid, under Opera there are issues with iframes nested in tables and therefore the size of the RadWIndow is larger than expected. So far we have not found a viable solution for this and Opera's debugging tools are far from excellent.

As for the last code you sent - the RadWindow that is too-large in Opera - this is exactly the issue that is discussed in the previous post you linked and there is still no workaround for this. The good news is that it works correctly in all other browsers (the RadWIndow's height is 215px) and Opera's market share is about 2%. To answer the explicit question - no, I do not see anything wrong with the code. Maybe only the isVisible check, isClosed could be a little more robust sometimes.

On the original code you sent - indeed, I was able to observe this behavior, but I am sorry to say that I cannot provide any further information on the origins of this behavior (see the old post I am mentioning for the third time already I think). Since setting the ReloadOnShow to true provides consistent results (although a little wrong in Opera) I would advise that you keep it this way.

What I can say in conclusion is that we are aware of the sizing issue in Opera, we are working on it and once a solution is found it will immediately be incorporated in the code.

Regards,
Marin
the Telerik team

Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward!
We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>

Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.