If the annotation and its label are out of the viewport (the plot area) and then use the PanZoomBar to scroll to it, the label is not displayed. It appears after the chart layout is updated (ex: resize or zoom).

The SelectStyle() method of the DefaultVisualStyleSelector is never called

Will be available in R2 2016 Release.

Depending on the zoom level and height of chart, sometimes the first (bottom) label of the chart is not rendered when the vertical axis is a categorical one and the plot mode is BetweenTicks or OnTicksPadded. 

When you try to set the LabelDefinition property in style it is not applied.

As a workaround you can create an attached property to which you can apply the custom definition and set it to the LabelDefinition property of the annotation in its OnPropertyChangedCallback.

MovingAverageIndicator doesn't recalculate its data points when a new item is added in its ItemsSource at runtime

Workaround:
To update the data points of the indicator reset its Period property when a new item is added in the ItemsSource. For example:

// add new item
var indicator = chart.Indicators[0] as MovingAverageIndicator;
var period = indicator.Period;
indicator.Period = 0;
indicator.Period = period;

Available in LIB version: 2016.1.21

If you change the axes of a series at runtime in the following order the axis won't be rendered as expected.
1. Set the series' VerticalAxis property to a new axis instance
2. Set the series' VerticalAxis property to another new axis instance
3. Set the series' VerticalAxis property to the axis' instance created in step 1

This is observed in a scenario with two chart series and only the axis of one of the series is drawn incorrect.

When step 3 is performed, the axis is drawn at incorrect position. Then if you resize, the axis will be repositioned but without any ticks or labels.

Available in LIB Version 2015.3.1123.

Workaround:
One way to work around this is to set the plot mode of the axis to OnTicksPadded. 

The position of non-positive values cannot be determined when using a logarithmic axis (due to the nature of the logarithmic axis, non-positive values are undefined). Currently the chart displays such points as if the value of the point is 1, which is not correct. The chart should not display these values at all.

A NullReferenceException is thrown when the Strategy of the series is set


Available in LIB version: 2017.2.605

When there are no data points in the bar series, the chart fails to retrieve a color for the marker of the legend item. This can be worked around by modifying the item template of the legend item. In the new template the binding of the Fill of the marker, should include not just the MarkerFill but TargetNullValue:

<DataTemplate x:Key="legendItemContentTemplate1">
 <StackPanel Orientation="Horizontal">
  <Path Fill="{Binding MarkerFill, TargetNullValue=#9B25B1}" Width="12" Height="12">
   <Path.Data>
    <Binding Path="ActualMarkerGeometry" 
      RelativeSource="{RelativeSource AncestorType=telerik:LegendItemControl}" />
   </Path.Data>
  </Path>
  <TextBlock Margin="2" Text="{Binding Title}" />
 </StackPanel>
</DataTemplate>


Will be available in Q2 2016 Release.

In scenarios where a series is removed and after that an axis1 is removed, the other axis2 is rendered incorrectly if a series is added and then axis1 is added back.

The Open and Close properties of the OhlcSeries' data points are not updated at runtime in a data binding scenario when you update the properties from the view model. The same applies also for the CandlestickSeries.



Available in LIB version: 2016.2.606

The data points are not rendered when the series' axis is set at runtime through a DataTrigger in the series' style. 

Note: The data points are rendered when the chart is resized or zoomed.

Workaround:
Change the resource type in the DataTrigger that changes the axis - instead of DynamicResource, use StaticResource. 

<telerik:CategoricalSeriesDescriptor.Style>
    <Style TargetType="telerik:LineSeries">
        <Style.Triggers>
            <DataTrigger Binding="{Binding Path=Axis}" Value="Left">
                <Setter Property="VerticalAxis" Value="{StaticResource AxisLeft}"/>
            </DataTrigger>
            <DataTrigger Binding="{Binding Path=Axis}" Value="Right">
                <Setter Property="VerticalAxis" Value="{StaticResource AxisRight}"/>
            </DataTrigger>
        </Style.Triggers>
    </Style>
</telerik:CategoricalSeriesDescriptor.Style>

The fix is available in LIB Version 2015.1.0420.

The fix is available in LIB Version 2015.1.0406.

An exception is thrown in design time when a RadCartesianChart is inside a RadExpander and no-xaml binaries are used in combination with VisualStudio 2010.

Available in LIB version: 2015.1.1603

When the values of the data points have great values and the axis has a very small manual range, the Path element does not render correctly and is at times not visible at all.

Workaround:
A possible way to resolve this is to use the Direct2DRenderOptions. The different render modes use a completely different rendering logic.
<telerik:LineSeries.RenderOptions>
 <telerik:Direct2DRenderOptions />
</telerik:LineSeries.RenderOptions>

An exception occurs in the VS designer when a RadPieChart is placed in a RadDocking's RadPane.

The fix is available in Q1 2015 SP Release.