If you define two UserControls in a project and you add two RadTabControls - one RadTabControl per UserControl, then in design-time you can only change the selection of one of the tab components.
Drag and drop from Visual Studio Toolbox to the designer area doesn't allow you to drop the corresponding control inside the content of the selected tab item.
To work this around, add a Grid panel with transparent background inside the RadTabItem's in XAML. You can do this also through the toolbox.
<telerik:RadTabItem x:Name="RadTabItem1" Header="Tab item 1">
<Grid Background="Transparent" />
</telerik:RadTabItem>
When you select the RadTabItems via Keyboard or Mouse, Narrator or other Accessibility tools like NVDA do no read the selected tab. This is a bug in the RadTabControlAutomaitonPeer / RadTabItemAutomationPeer's code. Usually screen readers read "Selected Tab One", "Selected Tab 2". This is how MS TabControl is read actually.
TabControl's TabItems aren't properly updated on attempt to change the theme palette variation runtime until any of the items is selected. Check the following video - https://www.screencast.com/t/jMj0EZqFfy.
There are several possible workarounds which include:
private
void
RadTabItem_PreviewMouseDown(
object
sender, MouseButtonEventArgs e)
{
if
(e.ChangedButton == MouseButton.Middle)
{
e.Handled =
true
;
}
}
When pressing the Alt key, the access key of a given element must be displayed. Inside the Header of a TabItem it is not. The issue is not reproducible with the standard MS TabItem. It seems that it is related to the Foreground binding of the control. There is a workaround as shown below. <telerik:RadTabControl> <telerik:RadTabItem > <telerik:RadTabItem.Header> <AccessText Text="_Tab 1" Foreground="{Binding RelativeSource={RelativeSource AncestorType=telerik:RadTabItem}, Path=Foreground}"/> </telerik:RadTabItem.Header> </telerik:RadTabItem> </telerik:RadTabControl>