John Townsley
Top achievements
Rank 1
John Townsley
asked on 29 Jan 2014, 04:42 PM
I have recently updated my browser to IE 11 and I have the latest version of the AJAX controls. It appears that your keyboard support for TabStrip no longer works in IE 11. I went to your demo and it appears not to work there either. http://demos.telerik.com/aspnet-ajax/tabstrip/examples/functionality/keyboardsupport/defaultcs.aspx
Thank you for looking into this.
John
Thank you for looking into this.
John
9 Answers, 1 is accepted
0
Hello John,
I tested the demo that you describe and it seems that this is a bug of the control. Thank you very much for paying attention to it. I will log it to our internal system so that our developers can inspect it further and fix it. You can also find your Telerik points updated for reporting this issue.
Regards,
Kate
Telerik
I tested the demo that you describe and it seems that this is a bug of the control. Thank you very much for paying attention to it. I will log it to our internal system so that our developers can inspect it further and fix it. You can also find your Telerik points updated for reporting this issue.
Regards,
Kate
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 UI for ASP.NET AJAX, subscribe to the blog feed now.
0
John Townsley
Top achievements
Rank 1
answered on 18 Jun 2014, 04:17 PM
Any news on when this bug will be fixed?
0
Hello John,
In order to fix the issue in IE11 a possible breaking change in the keyboard support of the RadTabStrip control should be introduced. With the current implementation and the way keyboard support works, this issue could not be fixed. We will evaluate all possible solutions, but we could not give you ETA when the problem will be fixed.
Thank you for your understanding and please, excuse us for the inconveniences caused by this issue.
Regards,
Aneliya Petkova
Telerik
In order to fix the issue in IE11 a possible breaking change in the keyboard support of the RadTabStrip control should be introduced. With the current implementation and the way keyboard support works, this issue could not be fixed. We will evaluate all possible solutions, but we could not give you ETA when the problem will be fixed.
Thank you for your understanding and please, excuse us for the inconveniences caused by this issue.
Regards,
Aneliya Petkova
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Iain
Top achievements
Rank 1
answered on 06 Mar 2015, 09:24 AM
Has there been any update to this issue, or is there a valid workaround?
0
Hello Iain,
We are planning to ship a lightweight RadTabStrip control, most probably in the next Q release, which will support keyboard navigation in IE11.
Thank you for your understanding and please excuse us for the inconveniences caused by this issue.
Regards,
Aneliya Petkova
Telerik
We are planning to ship a lightweight RadTabStrip control, most probably in the next Q release, which will support keyboard navigation in IE11.
Thank you for your understanding and please excuse us for the inconveniences caused by this issue.
Regards,
Aneliya Petkova
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Allan
Top achievements
Rank 1
answered on 14 Jan 2016, 10:29 AM
Was this ever resolved? We've recently upgraded from an older version to version 2015.3.1111 and doesn't look like the Access Keys assigned to tabs are working?
0
Hello Allan,
The access keys in the TabStrip can be configured through its FocusKey property placed inside the control's KeyboardNavigationSettings. Please note, you have to use the control in Lightweight mode in order to utilize this functionality:
More useful information on the matter can be found here: RadTabStrip Keyboard Support.
Regards,
Vessy
Telerik
The access keys in the TabStrip can be configured through its FocusKey property placed inside the control's KeyboardNavigationSettings. Please note, you have to use the control in Lightweight mode in order to utilize this functionality:
<
telerik:RadTabStrip
ID
=
"RadTabStrip1"
runat
=
"server"
SelectedIndex
=
"0"
RenderMode
=
"Lightweight"
>
<
KeyboardNavigationSettings
CommandKey
=
"Alt"
FocusKey
=
"Q"
/>
<
Tabs
>
<
telerik:RadTab
Text
=
"Examples"
>
</
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Configurator"
>
<
Tabs
>
<
telerik:RadTab
Text
=
"Default"
></
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Test"
></
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Final"
></
telerik:RadTab
>
</
Tabs
>
</
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Quick Start"
>
</
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Help"
>
<
Tabs
>
<
telerik:RadTab
Text
=
"Search"
></
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Topics"
></
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Troubleshooting"
></
telerik:RadTab
>
</
Tabs
>
</
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Purchase"
>
</
telerik:RadTab
>
</
Tabs
>
</
telerik:RadTabStrip
>
More useful information on the matter can be found here: RadTabStrip Keyboard Support.
Regards,
Vessy
Telerik
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
0
Allan
Top achievements
Rank 1
answered on 18 Jan 2016, 09:27 AM
I believe this only sets focus to the tabstrip and navigation can then be done with arrow keys and enter key?
Previously we were able to set an AccessKey attribute against each tab (Alt + key) which is what we are looking to retain. Has this been deprecated in newer versions of Telerik?
Previously we were able to set an AccessKey attribute against each tab (Alt + key) which is what we are looking to retain. Has this been deprecated in newer versions of Telerik?
0
Hi John,
Yes, the suggested configuration controls the focus of the whole Toolbar. The AccessKey functionality of each tab is not deprecated and you can configure the desired Access key for each tab. The Accesskey is supported both in Classic (with no IE11 support) and LightWeight render modes with the only difference that in LightWeight you have to configure also the TabIndex of the accessible tabs (needed for IE):
Regards,
Vessy
Telerik
Yes, the suggested configuration controls the focus of the whole Toolbar. The AccessKey functionality of each tab is not deprecated and you can configure the desired Access key for each tab. The Accesskey is supported both in Classic (with no IE11 support) and LightWeight render modes with the only difference that in LightWeight you have to configure also the TabIndex of the accessible tabs (needed for IE):
<
telerik:RadTabStrip
ID
=
"RadTabStrip1"
runat
=
"server"
SelectedIndex
=
"0"
RenderMode
=
"Lightweight"
>
<
Tabs
>
<
telerik:RadTab
Text
=
"Examples"
AccessKey
=
"1"
TabIndex
=
"1"
>
</
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Quick Start"
AccessKey
=
"2"
TabIndex
=
"2"
>
</
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Help"
AccessKey
=
"3"
TabIndex
=
"3"
>
</
telerik:RadTab
>
<
telerik:RadTab
Text
=
"Purchase"
AccessKey
=
"4"
TabIndex
=
"4"
>
</
telerik:RadTab
>
</
Tabs
>
</
telerik:RadTabStrip
>
Regards,
Vessy
Telerik
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