In a virtualized TreeView, after ExpandAll and scroll operations, there are gaps in the TreeViewPanel.
RadTreeViewItem.AutomationProperties.Name is not read correctly since version 2011.2
RadTreeView and RadTreeViewItem ExpandAll() method sets the IsExpanded property to True to all items even if an Item has no children to display. This causes an issue when using the DefaultImageSrc and ExpandedImageSrc properties as the last-level items will be displayed with an ExpandedImageSrc as their IsExpanded property it set to True. However, as these items have no children, they should use the DefaultImageSrc.
We have RadContextMenu in RadTreeView when we press the App key or shift+F10 the context menu opens as intended but it triggers the parent TreeViewItem hover effect
BindingExpressionError occurs in situations when the tree is virtualized and TemplateSelectors are used
RadTreeView is virtualized and we use ItemContainerStyleSelector. The style selector select styles which set have ExpanderStyle property. The ExpanderStyle is not applied. There is an attached project which can be used as a possible workaround, Available in Official Release R3 2016. REOPEN: The bug will be re-opened from 5 Dec 2016 internal build as well as in the official R3 2017 release. We reverted the fix for this bug due to performance hit we found in R3 2016. The workaround suggested in the attached project is still valid.
The children count is read incorrectly by MS Narrator
Cannot properly scroll when using StackPanel as ItemsPanel.
Root level items ItemTemplate is incorrectly set after virtualization when using HierarchicalDataTemplate with ItemTemplateSelector. This causes the second level items to use incorrect data template.
The Horizontal ScrollBar cannot be hidden/disabled in certain situatations, for example when TreeView is inside RadPanelBarItem
When BringIntoView is called while an item is expanding the BringIntoView target item may appear on the screen but be animated away from it. The TreeView will not retry to bring it into view again. Ideally the TreeVeiw should re-focus on the last BringIntoView target if possible once the animation is complete. Currently there are two workarounds: - Turn off the animations while expanding if BringIntoView will be called - Call BringIntoView for the given item once the animations has completed.