Fixes

• Inputs rendered inside the tree (e.g. an <input> in a modal) can now receive Space characters again. The tree's keyboard handler no longer intercepts keystrokes that originate from a nested form field or contenteditable element. (#377)

Fixes

• NodeApi action methods (toggle, select, activate, focus, edit, etc.) are now bound to the node, so passing them as callbacks — e.g. <Toggle onClick={node.toggle} /> — no longer throws "Cannot read properties of undefined (reading 'tree')" when invoked detached. (#374)

Features

• useSimpleTree now accepts an onChange option, called with the full data array after any internal move/create/rename/delete — a single place to persist the whole tree without wiring up each handler yourself. (#373)

Features

• Added a disableDeselectOnClick prop. By default, clicking the empty area below the rows clears the selection; setting this prop keeps the current selection intact instead (#245, #308). (#369)

Features

• TreeApi now exposes scrollToOffset(offset) to scroll the list to an exact pixel offset from the top, and a scrollOffset getter to read the current position — the offset-based counterpart to scrollTo(id), useful for saving and restoring scroll position (#194). (#368)

Fixes

• scrollTo (and the selection prop / tree.scrollTo() paths that use it) now scrolls horizontally as well as vertically, bringing a deeply nested node's indented content into view when rows overflow the tree's width. Previously only the vertical position was adjusted, leaving deep nodes off-screen to the right. (#367)

Fixes

• TreeApi methods (select, focus, delete, edit, node creation, etc.) now honor a custom idAccessor when given raw row data, instead of always reading .id. The identifier parameters and the onCreate return type accept your data type, so a custom accessor works end-to-end. (#366)

Fixes

• initialData now honors idAccessor and childrenAccessor (issue #73, also #170). The built-in data controller behind initialData hardcoded id and children, so trees keyed differently couldn't be reordered (drag ids never matched) and moving a node with children dropped them. The controller now reads ids and children through the same accessors as the rest of the tree. A string childrenAccessor is fully supported for reorder/create/delete; a function childrenAccessor is read-only, so write-back falls back to the children key. (#365)

Fixes

• A node can no longer be dragged while it's being renamed (issue #195). Previously, dragging inside the rename input picked the row up and moved it — visible even in the official Gmail demo. The drag source now refuses to start a drag while the node is in editing state, matching the VS Code explorer. (#364)

Fixes

• Dropping a dragged node in the empty area below the last row fires onMove again (issue #313). The drop logic had been moved into the per-row drop hook but never added to the outer (bottom-of-list) drop target, so drops to the very bottom of the tree were silently ignored. The shared handler now lives on tree.drop() and is used by both drop targets. (#361)