Test Environment:
OS: Windows_11URL: https://demos.telerik.com/aspnet-ajax/window/examples/windowmanager/defaultcs.aspx
Repro Steps:
Actual Behavior:
Focus comes out of 'delete' popup without closing it automatically.
Expected Behavior:
When opening the 'delete pop-up', focus is expected to move to delete pop-up controls and focus should not leave the pop-up until it is closed. When a pop-up is opened, focus should move into that item and when it is closed, focus should return to the same control that opened it. In addition, focus should be confined to the window until the user closes it with an action, such as the close button or the ‘ESC’ key.
The Window will not open in the center of the screen if it was already opened once and the page has been scrolled. It seems that the Window keeps opening at the same position initially was opened, hence it could open out of screen bounds.
Code
<style>
.mydiv {
margin: 2000px 100px;
}
</style>
<telerik:RadWindow ID="RadWindow1" runat="server">
<ContentTemplate>
<h3>RadWindow1 Content</h3>
</ContentTemplate>
</telerik:RadWindow>
<script>
function ShowEditForm(sender, args) {
var wnd = $find("<%= RadWindow1.ClientID %>");
wnd.show();
}
Sys.Application.add_load(function () {
setTimeout(function () {
$telerik.$('.mydiv')[0].scrollIntoView();
}, 100)
});
</script>
<div class="mydiv">
<telerik:RadButton runat="server" ID="RadButton1" Text="OpenWindow" AutoPostBack="false" OnClientClicked="ShowEditForm" />
</div>
AutoSize shows a scroll in Chrome.
See your own Window auto-size demo page
Here is a screenshot from your demo. See scroll-bars...you must slightly resize bottom right to make them disappear.
The predefined RadWindowManager dialog templates do not fully expose the required accessibility attributes.
Two issues are present in the default predefined dialog markup:
When AutoSize is enabled on a RadWindow, the calculated width and height of the window can be larger than the actual content requires. The extra size appears as dead space around the content, on the right side for width and at the bottom for height, and is most noticeable when the content or its wrapping container has its own padding or border.
Steps to reproduce:
Result:
The RadWindow is wider and/or taller than necessary. The extra space is not evenly distributed and shows up as unexpected empty space next to or below the content.
Expected:
The RadWindow width and height should match the actual content size, with the same behavior as before the 2026 Q1 release.