We use the RadDatePicker in numerous places. Sometimes direct and sometimes through a DataTemplate, but the problem is consistent. We can TAB through the controls (including other telrik controls) but we cannot SHIFT+TAB (reverse tab) through the date controls. It stops and highlights the date on the control and goes no further.
we are using 2014.2.729.45 for all controls.
below are some code samples:
And here is the Style
I saw this used to be an issue, but was corrected back in 2012. not sure if bug was re0introduced or we have some piece of code "off".
thanks.
​
we are using 2014.2.729.45 for all controls.
below are some code samples:
01.
<
WrapPanel
Grid.Row
=
"3"
02.
Grid.Column
=
"1"
03.
>
04.
<
telerik:RadDatePicker
SelectableDateEnd
=
"{Binding LineItemEndDate}"
05.
SelectableDateStart
=
"{Binding LineItemStartDate}"
06.
SelectedValue
=
"{Binding GivenStartDate}"
07.
Style
=
"{StaticResource TilePropertyDataRadDatePickerStyle}"
08.
/>
09.
<
ContentControl
IsEnabled
=
"{Binding IsStartDateInvalid}"
10.
Style
=
"{StaticResource ErrorAdorner}"
11.
ToolTip
=
"{Binding StartDateErrorMsg}"
12.
/>
13.
</
WrapPanel
>
And here is the Style
01.
<
Style
x:Key
=
"TilePropertyDataRadDatePickerStyle"
02.
TargetType
=
"{x:Type telerik:RadDatePicker}"
03.
>
04.
<
Setter
Property
=
"FontFamily"
Value
=
"{telerik:Windows8Resource ResourceKey=FontFamily}"
/>
05.
<
Setter
Property
=
"FontSize"
Value
=
"{telerik:Windows8Resource ResourceKey=FontSize}"
/>
06.
<
Setter
Property
=
"FontWeight"
Value
=
"Normal"
/>
07.
<
Setter
Property
=
"IsTabStop"
Value
=
"True"
/>
08.
<
Setter
Property
=
"Height"
Value
=
"{StaticResource TilePropertyHeight}"
/>
09.
<
Setter
Property
=
"Foreground"
Value
=
"{StaticResource TilePropertyDataBrush}"
/>
10.
<
Setter
Property
=
"Margin"
Value
=
"{StaticResource TilePropertyDataMargin}"
/>
11.
<
Setter
Property
=
"VerticalAlignment"
Value
=
"Center"
/>
12.
<
Setter
Property
=
"Width"
Value
=
"100"
/>
13.
<
Setter
Property
=
"HorizontalAlignment"
Value
=
"Left"
/>
14.
</
Style
>
I saw this used to be an issue, but was corrected back in 2012. not sure if bug was re0introduced or we have some piece of code "off".
thanks.
​