Completed
Last Updated: 24 Aug 2022 10:23 by ADMIN

Test Environment:

OS: Windows_11
Version: 21H2
OS Build: 22000.795
Browser: Version 103.0.1264.71 (Official Build) (64-bit)

URL: https://demos.telerik.com/aspnet-ajax/window/examples/windowmanager/defaultcs.aspx

Repro Steps:

  1. Open Telerik Web UI Window RadWindowManager Client-side API Demo | Telerik UI for ASP.NET AJAX.
  2. Locate "METHODS OPENING RADWIDNOWMANAGER DIALOGS" under "DEMO CONFIGURATOR".
  3. Under "METHODS OPENING RADWIDNOWMANAGER DIALOGS", open any button (for example, "Open radconfirm").
  4. Dialog opens.
  5. Keep pressing TAB inside the dialog.
  6. Observe the issue that the focus moves to the background content behind the dialog even though the dialog is still open. The focus should remain trapped within the dialog.

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. 

Unplanned
Last Updated: 10 Jan 2023 16:27 by Ricardo
Created by: Ricardo
Comments: 0
Category: Window
Type: Bug Report
0

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.

Steps & Code for Reproduction

 

  1. Copy/Paste the Code from below and Load the page
  2. Click on the Button, the Window will open at the center
  3. Scroll toward the top of the page until the button is barely visible
  4. Click the button again. At this point, the Window will open out of the screen boundaries, in its initial position

 

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>

Completed
Last Updated: 28 Jan 2026 10:30 by ADMIN
Release 2026 Q1 (Feb)
Created by: Sean
Comments: 1
Category: Window
Type: Bug Report
0

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.

Completed
Last Updated: 31 Mar 2026 10:06 by ADMIN
Release 2026 Q1 SP2

The predefined RadWindowManager dialog templates do not fully expose the required accessibility attributes.

Two issues are present in the default predefined dialog markup:

  • The RadAlert message container does not expose live-region semantics required by accessibility audit tools, e.g. role="alert" / aria-live behavior.
  • The RadPrompt input does not expose a sufficient accessible label in the default template markup.
Completed
Last Updated: 25 Sep 2026 13:25 by ADMIN
Release 2026 Q3 SP1

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:

  • Add a RadWindow with AutoSize="true" (any AutoSizeBehaviors).
  • Set the window content either through a ContentTemplate with inline markup (for example a RadAjaxPanel), or through NavigateUrl pointing to a separate page.
  • Give the content, or its wrapping container, a horizontal and/or vertical padding or border via CSS.
  • Open the RadWindow and let it auto-size.

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.

2 3 4 5 6 7