The application hangs when you click on a Label element placed in the DropDownContent of RadSplitButton. In order to recreate this the content of the Label should contain an underscore character, thus enabling the access text WPF functionality. Also, the CloseOnPopupMouseLeftButtonUp property should be set to True.

This behavior can be reproduced with any element that is not derived from FrameworkElement. The issue in this case appear because when the access text is enabled, the Label control produces Run elements in its visual tree. The Run class doesn't derive from FrameworkElement, but from FrameworkContentElement, which causes the issue.

To work this around, use TextBlock instead of Label.

QueryableEntityCoreCollectionView internal collections not in sync.

Currently, there is no workaround to this behavior.

Some dialogs like ParagraphPropertiesDialog and SectionColumnsDialog have dependency properties for defining the width of the numerics. When creating implicit style, the value of these custom properties results in 0 and they are invisible in the UI.

Workaround: Set the value of the property in the custom style. For paragraph properties dialog:

<Style TargetType="rtb:RadParagraphPropertiesDialog" BasedOn="{StaticResource CustomStyle}" >
    <Setter Property="NumericWidth" Value="85"/>
</Style>

When opening the ContextMenu and hovering over the first Item no Tooltip is displayed. Only when you move the mouse over another MenuItem on the same ContextMenu and then back to the first one the Tooltip gets displayed.

As a workaround, the telerik:RadToolTipService.ToolTipContent property can be used:

<telerik:RadMenuItem Header="I should display a tooltip" telerik:RadToolTipService.ToolTipContent="I am the tooltip that never shows" />

The template of the tooltip can also be modified to match the default tooltip style:

    <Style TargetType="telerik:RadMenuItem" BasedOn="{StaticResource RadMenuItemStyle}">
        <Setter Property="telerik:RadToolTipService.ToolTipContentTemplate">
            <Setter.Value>
                <DataTemplate>
                    <Border
                                Background="{telerik:FluentResource ResourceKey=PrimaryBackgroundBrush}"
                                BorderBrush="{telerik:FluentResource ResourceKey=BasicBrush}"
                                BorderThickness="1"
                                SnapsToDevicePixels="True">
                        <ContentPresenter Content="{Binding}" Margin="5"/>
                    </Border>
                </DataTemplate>
            </Setter.Value>
        </Setter>
    </Style>

The WorkbookContentChanged event is invoked right after importing a document. 

When a RadGridView cell has a validation error, a red border will appear around the cell. In this case, the top validation border is missing on the first row cells. As a workaround, you can move the ContentPresenters of the cells a little bit in the loaded event of the control.

private void RadGridViewView_Loaded(object sender, System.Windows.RoutedEventArgs e)
{
    var treeListView = sender as RadTreeListView;
    var editorPresenters = treeListView.ChildrenOfType<ContentControl>().Where(x => x.Name == "PART_ContentPresenter" && x.ParentOfType<GridViewCell>() != null);
    foreach (var item in editorPresenters)
    {
        item.Margin = new System.Windows.Thickness(1);
    }
}

Due to excessive memory consumption when decoding images, OutOfMemoryException can be thrown when viewing documents with large images inside them. 

Workarounds: 
- Set ExtensibilityManager.MaxImageSize = null. This will skip one resizing step, and could be beneficial in documents containing few large images.
- Use 64-bit process for the client application. This allows the process to consume much more memory. Note that starting 64-bit process while debugging can be tricky, as described in this blog post: https://weblog.west-wind.com/posts/2016/Dec/19/Visual-Studio-Debugging-and-64-Bit-NET-Applications.

Available in R1 2018 Official release version.

When a chart have long labels on the X axis (like date and time) the zoom is not accurate on the horizontal extents with both mouse wheel and drag area.

The reason is probably that the screen coordinates of the selected area are not mapped correctly on the X axis. The mapping works fine for tooltip.

You can verify this behavior in the attached Solution. In the images you can see the selected area (01), that the zoomed area is a region with no points (02) and the actual position of the points.