Tabbing problem in Rad Window popup

6 posts, 0 answers
  1. Afroz khan
    Afroz khan avatar
    38 posts
    Member since:
    Dec 2009

    Posted 19 Aug 2013 Link to this post

    Hi Team,

    I have a Rad Window popup, when i do tabbing then it works proper from top to bottom but after reaching tabbing in  last control, tabbing goes to URL, how can keep tabbing only inside the  Rad Window popup, also it should not goes to URL

    Thanks
    Afroz Khan
  2. Marin Bratanov
    Admin
    Marin Bratanov avatar
    3602 posts

    Posted 19 Aug 2013 Link to this post

    Hi Afroz,

    We are aware of a problem that caused the input in the statusbar of the RadWIndow (where its URL is shown) to get focus while tabbing through the page and it has bee fixed. This fix should be available in tomorrow's LIB and in the Q3 2013 release. A temporary workaround can be hiding the statusbar of the control.

    If you are referring to the address bar of the browser itself - this is behavior we cannot and should not control. Keyboard navigation in the OS should not be prevented by the page and this letting the user focus the address bar of the browser with the keyboard is an accessibility feature of the browser, not of the page it loads.


    Regards,
    Marin Bratanov
    Telerik
    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 the blog feed now.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Afroz khan
    Afroz khan avatar
    38 posts
    Member since:
    Dec 2009

    Posted 23 Aug 2013 Link to this post

    Thanks
    A different problem came with window popup, after reaching the tab index into last control, next tab index is moving into parent page control, after tabing from parent control , it is moving into URL
    Could you please help ,how can i prevent tabing from window popup to parent control?
  5. Marin Bratanov
    Admin
    Marin Bratanov avatar
    3602 posts

    Posted 26 Aug 2013 Link to this post

    Hi Afroz,

    We are aware of an issue with a RadButton getting focused when it is in the main page behind a modal RadWindow, and if this is not your case I would advise that you share some code that leads to the problem and perhaps a short video that shows the process that can be used to reproduce the problem. This will let us inspect it and see what is going on.


    Regards,
    Marin Bratanov
    Telerik
    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 the blog feed now.
  6. techQ
    techQ avatar
    1 posts
    Member since:
    Mar 2015

    Posted 23 Mar 2015 in reply to Marin Bratanov Link to this post

    Hi Marin,

    I have the same problem as the focus from last control in a radwindow moves to browser url , then it will navigates to parent page.
    Do you have any work around or fix ?
  7. Marin Bratanov
    Admin
    Marin Bratanov avatar
    3602 posts

    Posted 24 Mar 2015 Link to this post

    Hi,

    The fact the the focus moves through the browser chrome (address field, any buttons and menus there) is expected and cannot be avoided. Actually, preventing it will prevent users from being able to use their computers with the keyboard, so it is not desired.

    As for focus going into the page behind a modal RadWindow - RadWindow is merely a collection of HTML, CSS and JavaScript. What its modal feature does is the following:

    • add a div element that consumes clicks and is semi-transparent, so users cannot interact with the background page via the mouse
    • go through all elements on the page and reset their tabIndex to -1 so they cannot be focused through the keyboard.
    • restores the tabIndex initial values when closed

    This is the extent to which modality can be mimicked through JavaScript. True modality can only be achieved with the native capabilities of the browser (e.g., see the alert() dialog). You cannot, for example, prevent the HTML (or Body, depending on the browser) element from being focused, as the browser does that when its chrome is focused.

    You can easily test this with the following page. Clicking the Tab key will focus the browser chrome and at this point the HTML element will be focused:

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
     
        <head runat="server">
            <title></title>
            <style type="text/css">
                html:focus
                {
                    border: 2px solid red;
                }
            </style>
        </head>
        <body>
            <form id="form1" runat="server">
                <input type="text" />
            </form>
        </body>
    </html>

    where you can swap html:focus with body:focus for different browsers and add the tabIndex="-1" attribute to the input. 

    Regards,

    Marin Bratanov
    Telerik
     

    See What's Next in App Development. Register for TelerikNEXT.

     
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017