If the TreeView dataSource gets an error on a read request, the TreeView displays the "Request failed. Retry" message. However, on a subsequent successful request, the TreeView is not refreshed.
The TreeView should be refreshed on a subsequent successful request.
Currently you have to run this snippet to force only 1 selection from a tree. https://www.telerik.com/forums/allow-only-single-checkbox-to-be-checked-at-a-time#sky4SuHN70Cbrnl-6cNnhg I would suggest this be added as a configuration option of the tree. something like singleSelect: true
Drag & Drop multiple nodes in a treeview from one parent to another.
If i have lots of children nodes that i need to move from one parent to another I have to do one at a time... it will be usefull to select multiple nodes and
in one single drag&drop do the shift.
The expandTo and expandPath methods of the TreeView do not change the data-expanded and aria-expanded attributes to "true".
After the items are expanded, their data-expanded and the aria-expanded attributes are false.
After the items are expanded, their data-expanded and the aria-expanded attributes should be set to true.
As explained at http://www.telerik.com/forums/paging-a-treeview, paging in a treeview is not support. However, this feature would be highly useful for nodes that have hundreds of children, when the user may not want to way for all of them to be loaded or displayed at one time. See by contrast Webix pager for trees - http://docs.webix.com/api__link__ui.tree_pager_config.html
There is an accessibility issue regarding MAS 4.2.1 - Object Information.
Using keyboard navigation and screen reader (Windows Narrator),
While the focus is on expanded tree item (with inner children), screen reader should not read all the children information in one go, it should read one by one.
See the attached video.
Can you help please?
A recent update added the Checkbox widget that uses a novel set of CSS and HTML elements to stylize the checkbox in the browser. This style is not automatically applied to the TreeView widget's checkboxes. It would be very nice to have the TreeView checkboxes stylized to maintain a consistent look and feel across widgets: http://docs.telerik.com/kendo-ui/web/appearance-styling#checkboxes-and-radio-buttons
:upon selecting an item, either by click or programmatically, $(tv).scrollIntoView(item) with would bring the item into view, even in multilevel nested, hierarchical, situations. that would be very sweet!! I have tried JQuery.scrollTo but have had no success in nested <li> scenarios. thanks item will scroll into view
I am using Kendo tree view with drag and drop feature enabled in it. I am facing problem with it in my Samsung note 10 mobile. Where a normal swipe on the phone with the tree view is picked up as a drag and drop. Is there a way to differentiate between these two.
When drag and drop is enabled in a treeview, dragging a node from one treeview to another adds it to the other tree and removes it from the first. It would be nice if the move could also be specified as a 'copy' (leaving the source untouched).
It would be great, if I get a feature to allow to drag multiple selected nodes from treeview to drop to Treelist nodes. I need this by using MVC telerik not Kendo
We noticed an issue with our Numeric TextBox after a recent upgrade on Chrome. We're currently on Version 73.0.3683.86 (Official Build) (64-bit), the latest version at the time of writing. Our setup has a grid using a TreeView as an editor template. The TreeView, in turn, uses a NumericTextBox inside its item template. I've prepared a working demo that illustrates the issue. If you click on the last column of the grid, expand the TreeView and click on one of the NumericTextboxes, you will see that it loses the focus as soon as you click on it. As a result, it's impossible to input anything into those fields. Any other browsers don't have this issue.
We had a lot of issue reports from our clients this week so we're pretty sure it's a recent update from Chrome. Please let me know if you need further clarification. This is a fairly serious issue for us as it's affecting one of the main functionalities of our web application. If you can provide a temporary workaround before the proper fix comes out, that'd be great.