Bug 1:

When RadWindow behavior is set to Maximize/Minimize only, the expected behavior is while minimized, it must only show Maximize button and when maximized, it should show minimize button. 

Currently, it is showing restore button on minimizing and then it restores to a random size.

Bug 2:

Page reloads on maximizing the minimized page.

1. If the page requires authentication, the user has to login again.
2. If the user is on some of the internal pages on a portal, the user is redirected to the login page without referer URL.

The content scrollbars of RadWindow are not shown in Lightweight if ShowContentDuringLoad="false". The bug is specific to Chrome.
----------------------------------------
Workarounds:

1. Use the control in RenderMode=Classic

2. Enable the ShowContentDuringLoad="true" property

3. or attach a handler to the RadWindow's OnClientPageLoad proeprty and call the restore() method of the control in it:

        <telerik:RadWindow RenderMode="Lightweight" ID="RadWindow1" ShowContentDuringLoad="false" VisibleOnPageLoad="true" Width="600px" Height="400px" Title="Wikipedia" OnClientPageLoad="onLoad"
            NavigateUrl="https://www.wikipedia.org" runat="server">
        </telerik:RadWindow>
        <script>
            function onLoad(sender, args) {
                sender.restore();
            }
        </script>


----------------------------------------
Steps to reproduce:

1. Run the following code:

        <telerik:RadWindow RenderMode="Lightweight" ID="RadWindow1" ShowContentDuringLoad="false" VisibleOnPageLoad="true" Width="600px" Height="400px" Title="Wikipedia"
            NavigateUrl="https://www.wikipedia.org" runat="server">
        </telerik:RadWindow>

Result: No scroll bars are shown, they apper after moving the window

At present, when a RadWindow is pinned, it still uses position: absolute and an interval is initiated to recalculate its position every 100ms. This causes it to visibly "jump" when the user scrolls the page because of the interval update in its location.

Instead, position: fixed should be used to avoid the position calculation on an interval.

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.

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).