We are trying to make our website accessible using Wave and one thing we are struggling with is TreeViews with checkboxes enabled. Sometimes the checkbox is rendered as a span element and sometimes as an input element. In the second case Wave is recognizing an error for each node as the input element is not associated with its neighbouring text. You can see this on your own website: https://demos.telerik.com/aspnet-ajax/treeview/examples/functionality/checkboxes/defaultcs.aspx. For the server side tree the checkboxes are rendered as inputs and there is no label associated with it.

This behaviour doesn't change when I set EnableAriaSupport="true".

In Classic RenderMode, Windows7 skin, TreeView nodes are higher when inside ContentTemplate of RadPanelBarItem:

The ClientNodeClicking and server-side NodeClick events are triggered when tap-to-scroll the Treeview in Android (taphold event).

Steps to reproduce:
1. Open http://demos.telerik.com/aspnet-ajax/treeview/examples/overview/defaultcs.aspx in mobile Chrome of Android device (or in Chrome emulator)
2. Tap over a node to Scroll the Treeview

Result - the tapped node gets selected

Expected - the Treeview detect the tap from holdtap events and the node is not selected when scrolling occurs

http://screencast.com/t/CySy2iAoiG4n

The TreeView wrapper is not expanded depending on its nodes width when used in LightWeight render mode. As a result of that the horizontall scrollers of the control's parent element are never shown thus the nodes of the control appear truncated.


The problem can be reproduced with the following configuration:
ASPX:

        <div style="width: 100px; height: 400px; border: 1px solid black; overflow: auto;">
            <telerik:RadTreeView ID="RadTreeView" runat="server" RenderMode="Lightweight">
            </telerik:RadTreeView>
        </div>

C#:

    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
            string[] cars = new string[] { "Porsche Carrera", "Ferrari F430", "Aston Martin DB9 and some more words foe a long node" };
            RadTreeView.DataSource = cars;
            RadTreeView.DataBind();
        }
    }

At the moment when disabling a RadTreeNode on server/client side the complete node gets disabled with the CheckBox.
We had a use case where we would like the node to stay functional (collapsable/expandable/clickable/hover-effect) but only the checkbox to become disabled.
As this can't be achieved with the RadTreeView we had to build a work-around for that. Most likely people in need of this feature make a new HTML-variable to store/transmit/apply the state of the checkbox since the manipulation of the Checkboxes gets lost in a postback.

This would have to be implemented as a server/client-feature as it is with the enabled/disabled-state of the RadTreeNode.

Kind regards

The RadTreeView adds a CSS class to selected nodes "rtSelected".  Is it possible to fire an event then, since you know when you are adding that class?

If I were to do a jQuery each on the <li> elements and subscribe to changes in the attribute "Class" I could probably mimic similar behavior.  

I have noticed this feature has been desired for several years.  
The work-arounds suggested by your staff are basically to capture onKeyPressing event and check for a newly selected node after a setTimeout.  This works but is more like a hammer to kill a fly.

Thank you
Sean

I think that TreeView incorrectly handles the case of  a drop beneath a node that is expanded.

When a node (with or without children) is _not_ expanded, then dropping directly beneath (meaning lower down on the page) that node indicates that the node should be made the next sibling of the node.

-  A
+ B
------   <- Drop indicator means that dropping here will cause the dropped node to be the next sibling of B, which makes sense.
-  C

This case makes perfect sense.

However, when the node is expanded, the drop indicator doesn't change it's behavior, and I think it should.

-  A
+ B
------   <--- Dropping here will cause the dropped node to be the next sibling of B, but this is not visually where it will appear in the tree.
    - B.1
    - B.2
<--- This is where the node will appear after drop.
-  C

This is counter-intuitive to most people.  People think that dropping between B and B.1 would make the dropped item to become a child of B and a prior sibling of B.1.  But instead, it has the same effect as if the B node wasn't expanded and adds the new dropped node as the next sibling of B.  Note that in this case, the newly dropped node doesn't show up where it was dropped.  When a node doesn't appear in the tree where it was dropped, people assume that that's a bug. 

To see the issue, go here:

http://demos.telerik.com/aspnet-ajax/treeview/examples/functionality/draganddropnodes/defaultcs.aspx

In the "RadTreeView1" treeview, try to drag the "Deleted Items" item to be the last item in the list (but not a child of "Search Folders").  If you drag toward the bottom of the tree, after you drag down past "Unread Mail", you see the drop indicator that shows that you can drop to make it be the next sibling of "Unread Mail".  If you keep dragging down, you _don't_ see an indicator that you can drop to make the next sibling of "Search Folders".

However, if you drag between "Search Folders" and "Form Follow Up", then you _will_ see an indicator that shows that the item will be made the next sibling of "Search Folders".  And if you drop there, it will indeed be made the next sibling of "Search Folders", but of course it will appear at the bottom of the tree (not where you dropped it).

The kendo TreeView has the same behavior as the RadTreeView.  However, I have found some TreeViews that handle it in the way I would prefer.  See http://mbraak.github.io/jqTree/  for an example.