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();
        }
    }

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

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".