RadWindow controls lose focus with RestrictionZoneID

3 posts, 0 answers
  1. John
    John avatar
    43 posts
    Member since:
    Aug 2014

    Posted 25 Sep 2015 Link to this post

    Utilizing: ASP.Net AJAX Q3 2014 

    I'm opening windows, containing an aspx page, with various controls (combo, text, numeric, datepicker, etc.).  The RadWindowManager is set to KeepInScreenBounds="true" and RestrictionZoneID="ContentPane".  When running it on my Windows 7 desktop, it works great.  When running it on my Windows 8.1 ​Windows Surface Pro 3, the page controls lose focus after I click in the text entry box.  It then refreshes the window and doesn't allow me to change the value in the text box.  If I click on a RadComboBox, it fires the query and displays the dropdown; but, when I click on the text box to change the combobox value, it doesn't allow me to change the value in the text box..  This only applies to pages that are contained in a RadWindow, when running on a Windows Surface.  The problem might be specific to Windows 8.1; but, I don't have another 8.1 machine to test it.  Other aspx page controls work fine.  If I take the problem page and run it as a stand-alone page, without RadWindow, it works fine.  If I remove the RestrictionZoneID property from the RadWindowManager, the controls no longer lose focus; but, of course, I lose the ability to KeepInScreenBounds.  By the way, I get the same result whether I use the fancy RadWindow properties (below), or not.  In other words, if I just use ... <telerik:RadWindow ID="AssetCreateDialog" runat="server">, I get the same result.




    <telerik:RadWindowManager ID="RadWindowManager2" runat="server" EnableShadow="true" Style="z-index: 12345" KeepInScreenBounds="true" RestrictionZoneID="ContentPane">


    <telerik:RadWindow ID="AssetCreateDialog" runat="server" Title="Create Asset" Height="650px" Top="50px"
                    Width="800px" Left="125px"  ReloadOnShow="true" ShowContentDuringLoad="false"  VisibleStatusbar="false"  
                    Modal="true" Behaviors="Move, Resize, Close">


  2. Marin Bratanov
    Marin Bratanov avatar
    4533 posts

    Posted 29 Sep 2015 Link to this post

    Hi John,

    This is a known issue with the restriction zone and Surface devices: http://feedback.telerik.com/Project/108/Feedback/Details/38634. The only workaround we are aware so far is to remove the RestrictionZoneID property.

    The RestrictionZoneID feature itself poses some limitations (you can find them in the Common Issues help article) and it is not very suitable for modern sites that emphasize on responsiveness and adaptability according to the screen resolution.

    A RadWindow inherits the settings from its manager, so you can also try removing the restriction zone like this, in case you want to keep it for most cases:

    <telerik:RadWindowManager ID="RadWindowManager1" runat="server" RestrictionZoneID="ContentPane">
            <telerik:RadWindow ID="RadWindow1" runat="server" OnClientBeforeShow="removeRestrictionZone"></telerik:RadWindow>
    <asp:Button ID="Button1" Text="open wnd" OnClientClick="radopen('', 'RadWindow1');return false;" runat="server" />
        function removeRestrictionZone(sender, args) {
            if ($telerik.isIE && $telerik.isTouchDevice) {

    As for the KeepInScreenBounds property - it should work without a restriction zone as it is designed to be standalone.

    What I would also suggest is using the RenderMode=Lightweight setting because it improves the screen boundary and dragging detection.


    Marin Bratanov
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. John
    John avatar
    43 posts
    Member since:
    Aug 2014

    Posted 29 Sep 2015 in reply to Marin Bratanov Link to this post

    Martin, this solution looked really promising; however, in my app, the OnClientBeforeShow was causing my default homepage to scramble.  I tried with the associated javascript and blank; same result either way.  ​There m​ight be a conflict elsewhere.  For now, I'll remove the RestrictionZoneID all together, as it isn't critical.


Back to Top