If the content page has a title RadWindow should set it for its own title, unless its Title property has been set explicitly.

Since Q2 2013, when ShowContentDuringLoad=true (which is the default value) this does not happen.

The second workaround is using the OnClientPageLoad event:
			function OnClientPageLoad(sender)
			{
				try
				{
					var pageTitle = sender.get_contentFrame().contentWindow.document.title;
					sender.set_title(sender.get_title() == "" ? pageTitle : sender.get_title());
				}
				catch (err)
				{

				}
			}
The try-catch block is used to catch errors in case the page is from another domain and the JavaScript same-origin policy is in effect.

The event handler can also be attached to the RadWindow manager so that it will be used for all its RadWindows.

After added this code window close button stop working.

if we remove these three properties it works fine
        oWnd.SetWidth(width);
        oWnd.SetHeight(height);
        oWnd.center();


function openWin(url) {
        var oWnd = radopen(url, "RadWindow22");
        oWnd.SetWidth(width);
        oWnd.SetHeight(height);
        oWnd.center();
    }

Currently, when a maximized RadWindow is closed the OnClientCommand event handler is called with a command "Restore" because when a maximized RadWindow is being closed it is first restored.



A flag can be used to avoid it, see the attachment.

Instead, the dimensions the popup will have when restored are returned. This is so because a maximized RadWindow will resize with the browser.

A possible workaround is using the Telerik Static Client Library: http://www.telerik.com/help/aspnet-ajax/telerik-static-client-library.html

			var wnd = $find("RadWindow1");
			wnd.maximize();
			var bounds = $telerik.getBounds(wnd.get_popupElement());
			alert(bounds.width);

Currently setSize() works for popups that are already shown. If setSize() is called before show() (or radopen() or open() from a RadWindowManager) the new size will not be respected on subsequent iterations.

I have a radwindow which opens as a modal popup when a button is clicked, in the initial stages the rad window was able to be dragged towards right and bottom, of the screen, even out of the screen bounds, i managed to fix that by setting the KeepInScreenBounds="true" RestrictionZoneID="dvContainerMain", where "dvContainerMain" is the main div within which all the parent controls come
but now when i resize the parent browser window to almost size less than radwindow size, rad window seems to behave weird, am not able to resize the radwindow even if the resize behavior  is set
Please let me know on this issue, 
seems like there is a bug when the RestrictionZoneID width is less than or close to the radwindow size 

Thanks
Tony Thomas

When the input inside RadWindow is focused the on-screen keyboard is shown, the page is scrolled so the input is into view above the keyboard and then the keyboard hides automatically. This is caused by using a RestrictionZone. Remove this property to avoid the behavior.

When using DOCTYPE //W3C//DTD XHTML 1.0 Strict//EN and setting height to 100px 
RadWindow AutoResize=True gives problems in IE10 by adding unnecessary scrollbars, and in Chrome, FF and Safari the window is to high (approx. 55px too much).

Refers to forum entry: http://www.telerik.com/community/forums/aspnet-ajax/window/autosize-behavior-question.aspx
(I used the same sample project to replicate the problem).

 Please see attached screenshot and project.

This will be an enumerator just like the Behaviors property. It should, however, list the behaviors that are not allowed for the control. The common use case is that the developer does not want his popup to be resizable, so he/she needs only DisabledBehaviors="Resize" instead of listing all others that should be allowed in the Behaviors property. 

Currently a page loaded through HTTPS will throw a warning that unsecure content is loaded if the IconUrl of the RadWindow is set with a relative path. This happens because the framework sets the URL without regard for the protocol. A workaround is to always use full urls (e.g. https://mysite.com/images/myIcon.jpg).

If possible, RadWindow should check the protocol and fix the URL so that such warnings are not shown.

When a RestrictionZone is used the RadWindows are not positioned correctly in all cases.
When the number of windows is low (e.g. below approximately 6) the dimensions set to the RadWindows are not optimal. In some cases not all the available viewport is filled even if the number of popups matches the needed (e.g. 6 instances should be able to cover the viewport, but they cover about 2/3 of its height).

There are several ways to work around this:
1) disable autosizing (set AutoSize to false)
2) move the RadWindow after autoziging finishes (see attached example for a demo):
			function OnClientAutoSizeEnd(sender, args)
			{
				var wndBounds = sender.getWindowBounds();
				//this is the case when the viewport is not sufficient for the RadWindow
				//so the RadWindow is as tall as the viewport
				if (wndBounds.height == $telerik.getClientBounds().height)
				{
					sender.moveTo(wndBounds.x - 9);
				}
			}

3) avoid autosizing for the subsequent page loads in the content page.
This can be done by setting AutoSize to false and additionally the following function attached to the OnClientPageLoad event will provide autosizing for the first load without positioning issues:
 			function OnClientPageLoad(sender, args)
			{
				if (!sender.hasBeenShown)
				{
					sender.autoSize(false);
					sender.hasBeenShown = true;
				}
			}

4)  use partial postbacks in the content page so that it is not fully reloaded and the autosizing logic is not fired again automatically.

Currently the video does not play, only audio is heard. If autosizing is disabled the video functions properly.
A possible workaround is to disable autosizing and manually call the autosize() method when the page is loaded for all other browsers:

<telerik:RadWindow runat="server" ID="rw1" VisibleOnPageLoad="true" NavigateUrl="PlayVideo.aspx"
    AutoSize="false" Width="700" Height="500" OnClientPageLoad="OnClientPageLoad">
</telerik:RadWindow>

 and

function OnClientPageLoad(sender, args)
{
    setTimeout(function ()
    {
        if (!$telerik.isMobileSafari)
        {
            sender.autoSize(false);
        }
    }, 0);
}

This is related to a browser bug in accessing the document.activeElement property inside an iframe under IE9 and IE10.

See this KB article for additional information and examples: http://www.telerik.com/support/kb/aspnet-ajax/window/modal-radwindow-in-radwindow-in-ie9-and-ie10.aspx .

There are several possible workarounds:
1) remove the Modal feature.
2) Replace the opening logic with the one from this thread ( http://www.telerik.com/community/forums/aspnet-ajax/window/opening-radwindow-from-the-server.aspx ) and add a small timeout before showing the RadWindow. Even 0ms could suffice so the browser has an active element
3) Replace the RadAjaxPanel with an ASP UpdatePanel with UpdateMode set to Conditional
4) Add a function that will provide a focused element and call it in the OnClientBeforeShow event of the RadWindow
5) Add that function and call it in the ResponseScripts of the RadAjaxPanel
 The function could look like this: function fixIE() { document.documentElement.focus();} where, of course, you can focus some other element on the page.

A sample is attached.

A ShowOnTopWhenModal property would have the effect that any modal RadWindow (Modal=true) will increase greatly its z-index, just like it does when it is maximized. This property should take precedence over a maximized RadWindow (i.e. it should increase the z-index to more than 100 000).

A possible workaround:

<style>
    .topWindow {
        z-index: 100001 !important;
    }
</style>

for a markup of:
<telerik:RadWindow ID="topWindow" runat="server"
    Width="500"
    Height="300"
    VisibleOnPageLoad="true"
    CssClass="topWindow"
    Modal="true"></telerik:RadWindow>

A sample page that shows how you can implement such functionality is attached.