Add 'None' to the selection mode enum

This issue is applicable to Silverlight ONLY!

We have a RadTreeView with following properties IsLoadOnDemandEnabled="True", IsVirtualizing="True" and SelectionMode="Extended" set.
We select an element, collapse his parent and select another item. At this point if we expand the previously parent, both the newly selected item and the the first selected item are selected.
It is not correct the first item to preserve its selection state.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

It should be possible to collapse certain items to filter them out. This should not affect the look or functionality of the 

This is already implemented => you can use the ItemVisibility property of the RadTreeView.

There should be a way to exclude the partially checked items from the CheckedItems collection. 
A a property can be added to specify whether they will be included.

Edit: Please avoid using this collection because it ihas never been implemented completely in the RadTreeView. In DataBinding scenarios, you can use CheckBox in the ItemTemplate of the RadTreeView. Approach can be found here =>
http://docs.telerik.com/devtools/wpf/controls/radtreeview/how-to/howto-tri-state-mvvm.html 
CheckedItems colelction can be implemented in the ViewModels, instead of using the built-in property.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

ExpandAll() is a UI operation which blocks the UI thread.

The TreeView should be able to figure out the Old / NewValue for its event args during editing.
====
======

Reason for deletion. In databound scenarios e.OldValue and e.NewValue refer to the same instance of the ViewModel which is expected. 

Saving the state of the ViewModels means creating an entire deep copy of the ViewModel. We believe there is no such control in the framework to save the states of its ViewModels during editing.

We have to admin, introducing public properties OldValue and NewValue of type objects for these event args is a bad design. This is a bug since these are public but we won't fix it due to the complexity (described above).

Dynamic change of the DataContext does not reflect the DataContext of the TreeViewItems.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

DataTriggers that apply DefaultImageSrc, ExpandedImageSrc don't work when the TreeView is virtualized.
Reason for deletion:
The workaround is easy - just bind the DefaultImageSrc, ExpandedImageSrc to string properties from the ViewModel.
Also, a possible fix would slow down the virtualization process in the RadTreeView.

If the TreeView SelectionMode is Extended, dragging a single selected item while holding the Ctrl key will deselect the item

Available in Q1 2015

When the TreeView's ScrollViewer is Visible, changing the tree's width to 0 them back to Auto breaks the scrolling function of the ScrollViewer.
The workaround is to make the TreeView Collapsed before setting the Width to 0 and make it Visible before setting the Width back to Auto.

Another workaround: Use visibility instead of Width=0.

When the ScrollViewer of a virtualized TreeView is visualized the bindings of the TreeViewItem are broken.

We are closing this one because of duplication with the following item => http://feedback.telerik.com/Project/143/Feedback/Details/112754-treeview-bindingexpressionerror-occurs-in-situations-when-the-tree-is-virtualiz 

The CheckedItems  collection is not cleared when ItemsSource is changed.

Please consider CheckedItems as not supported collection in RadTreeView. In DataBinding scenarios , use the approach described in the following article:
http://docs.telerik.com/devtools/wpf/controls/radtreeview/how-to/howto-tri-state-mvvm.html 
This way you will be able to create CheckedItems property in your ViewModels.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

The TreeView doesn't update the TriState of the parent item when an item is dragged and dropped.

In databound scenario the built-in checkbox and the tri-state mode are considered not supported and users are prompted to use checkbox in itemtemplate with 3state logic in the viewmodels.
http://docs.telerik.com/devtools/wpf/controls/radtreeview/how-to/howto-tri-state-mvvm.html 

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

Create localization resources for the DropActionText in the TreeViewDragVisual element. The localization resources should work as the TextDropAfter, TextDropBefore, TextDropIn and TextDropRoot properties used to work in the Legacy mode of the RadTreeView DragDrop.

CheckState of the RadTreeViewItem is lost when a child item is added programmatically in the Items Collection. When the Items collection is just rechanged ( Items  = new ObservableCollection<DataItem>) checkstate is NOT lost.

Please use CheckBoxes in DataTemplates.


The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

SelectedItem property should not accept RadTreeViewItem objects when is data bound.

Reason for decline:

Ability to temporary view particular element as root item. Functionality have to be similar to "View this as root" in the Solution Navigator window in Productivity Power Tools for Visual Studio.

This is too custom requirement that can be implemented as application logic. 
Setting fildetered itemssource and preserving the current itemssource could be a possible solution.

If virtualization is enabled, the RadTreeView resets the IsExpanded state of the root items to 'false' upon binding when child items are created.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

"InvalidOperationException - The specified Visual and this Visual do not share a common ancestor" exception is thrown in scenarios where the RadTreeView ItemsSource collection is modified.

The bug is not reproducible with Q2, Q3 2014 version of telerik UI.

When the RadTreeViewItem (or the RadTreeView) is disabled and after a delay is enabled again it should go in "Normal" state. Now the control preserves its state, hence you are able to send more than one RadTreeViewItem in "Hovered" state.

The fix will be included in Q2 2015 SP.