I am sorry to say that for the restriction zone of the RadWIndow is static and its size must be set in pixels. Browser resizing is not supported with it for a number of reasons. What they have is a complete control focused on that task, while our RadWIndowManager is focused on dynamic (runtime) popup generation and flexibility.
Nevertheless I can suggest several things that can get you closer to this experience:
- put the tabstrip at the bottom
- follow this KB article
on resizing RadWindows with the browser
- you can iterate through the Windows collection of the manager and check isVisilbe() for each one before manipulating it. See the RadWIndow Client-side API
and RadWIndowManager client-side API
. You can take into account the tabstrip size in the calculations
- you can also disable the Maximize Behavior
as you already simulate it with code.
The drawback is that there will be no restriction zone in this case, yet the KeepInScreenBounds can compensate for that. You may also want to set a very big z-index for the tabstrip to keep it on top of RadWindows should the user drag them down.
Should you decide to work on that and manage to create a working solution you can post it in the Code Library
we have. We will be more than happy to award your work with Telerik points.
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed