Tom Rasmussen
Top achievements
Rank 1
Rank 1
Tom Rasmussen
asked on 29 Sep 2016, 08:12 PM
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.
4 Answers, 1 is accepted
0
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
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.
0
Tom Rasmussen
Top achievements
Rank 1
Rank 1
answered on 03 Oct 2016, 04:26 PM
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?
0
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
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.
0
Tom Rasmussen
Top achievements
Rank 1
Rank 1
answered on 04 Oct 2016, 03:31 PM
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.