Disabled PanelBar Keyboard Navigation

5 posts, 0 answers
  1. Tom Rasmussen
    Tom  Rasmussen avatar
    20 posts
    Member since:
    Jan 2009

    Posted 29 Sep Link to this post

    Is it possible to disable the keyboard navigation on a PanelBar?  I am trying to bind keypress to a radtextbox within an item's ContentTemplate and it is not recognizing the enter press.  I believe this is due to the keyboard navigation feature of the PanelBar overriding the action for specific keycodes.
  2. Anton
    Admin
    Anton avatar
    61 posts

    Posted 03 Oct Link to this post

    Hello Tom,

    If you want to disable keyboard navigation:

    1. Don't set the KeyboardNavigationSettings for the RadPanelBar.
    2. The TabIndex property does not have to be set.

    As for the issue that you experience - it is a known bug in the control that is already fixed and will be included in  our next service pack or latest internal build.

    Like that you won't be able to navigate your RadPanelbar with the keyboard.

    Regards,
    Anton
    Telerik by Progress
    Do you need help with upgrading your ASP.NET AJAX, WPF or WinForms projects? Check the Telerik API Analyzer and share your thoughts.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Tom Rasmussen
    Tom  Rasmussen avatar
    20 posts
    Member since:
    Jan 2009

    Posted 03 Oct in reply to Anton Link to this post

    It seems like the keyboard navigation is enabled b y default.  I have not set anything for KeyboardNavigationSettings yet I can use the arrow keys, space bar, enter, etc. to navigate within as long as it has focus.  If the issue of binding keypress and detecting enter is going to be fixed in the next that is great.  Is that in 2016.3.927?
  5. Anton
    Admin
    Anton avatar
    61 posts

    Posted 04 Oct Link to this post

    Hi Tom,

    If you are using Internet Explorer, the keyboard will be enabled by default. This is because the browser allows focus to be set to elements without TabIndex or AccessKey set. Unfortunately we don't have control over this browser quirk. 

    In any other browser if you don't set TabIndex or AccessKey, the keyboard support will be disabled.

    About your second question - unfortunately, the bug won't be fixed in 2016.3.927.

    Regards,
    Anton
    Telerik by Progress
    Do you need help with upgrading your ASP.NET AJAX, WPF or WinForms projects? Check the Telerik API Analyzer and share your thoughts.
  6. Tom Rasmussen
    Tom  Rasmussen avatar
    20 posts
    Member since:
    Jan 2009

    Posted 04 Oct Link to this post

    Thanks Anton.  I was actually using Chrome with my testing, but since the nav is separate from the issue in question, I won't worry about it.  I will implement another solution until the bug is fixed.
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017