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.
Thanks to your valuable feedback, I've updated the status of the feedback item to Approved.
The implementation and the decision whether and when will it be implemented depends on the popularity of this item. If more users vote for it, we'll raise its priority in the backlog.
Best
Regards,
Rumen
Progress Telerik
Hi Rumen,
Thanks for the workaround.
I can understand the developer who developed it 10 years ago might have missed something very important. It can be corrected as and when we grow.
We are developing the toolset for end-users who are mostly using MS windows. Hence, end-users will be more comfortable seeing RadWindow behave the same
I would be happier to have the bug fixed in the control itself then to write javascript to get it fixed.
Hi Kasim,
Thank you for the update!
The UX/UI of RadWindow is designed more than 10 years ago and the designers have chosen to show only the restore button when the component is minimized or maximized regardless of the Behaviors settings. This is because RadWindow does not mimic the MS Windows Dialog which work and directly interacts with the taskbar. We do have such an example RadWindow and MDI.
If you'd like to have the maximize button, when the control is minimized and vice versa you can use the OnClientCommand event, check for the enabled behaviors with the get__behaviors() method and set the desired behaviors with the set_behaviors() method.
The set_behaviors() method sets the Behaviors property of the RadWindow . Its argument must be a value or combination of values from the Telerik.Web.UI.WindowBehaviors enum. To set more than one behavior, use "+". Possible values are: None , Resize , Minimize , Close , Pin , Maximize , Move , Reload , Default . For example: oWnd.set_behaviors(Telerik.Web.UI.WindowBehaviors.Move + Telerik.Web.UI.WindowBehaviors.Close).
You can find more details at https://docs.telerik.com/devtools/aspnet-ajax/controls/window/client-side-programming/radwindow-object#methods-that-check-a-condition-or-invoke-a-certain-behavior.
Regards,
Rumen
Progress Telerik
Hi Rumen,
I differ on your comment #1. For any window user minimizes; the user expects a button to Maximize. Here the restore button is optional. The user is frustrated when she does not see the maximize button.
In current RadWindow implementation, to maximize RadWindow from the minimized state, the user needs to follow steps as below:
Also, when the restore button is clicked on, the expectation is it should restore to the size specified, however, it restores to a random size which is a clear bug.
The second scenario is when a portal page with form-based authentication is opened in the Radwindow, it prompts for login each time user minimize and maximize the window.
Hi Kasim,
Straight to the points:
Regards,
Rumen
Progress Telerik