the current tree has a hard coded delay of 300ms before updating the scroll position (and rendering new tree items) in case new tree items are loaded.
This delay is either wasting time (if the server responds fast), or causing problems under higher latency as shown in ZK-4834.

The current implementation even waits for 300 when there is no network activity involved. The rendering on demand is delayed for no apparent reason in this case.

A more robust way to synchronize the scroll position avoiding unnecessary delays would be preferable.

The attached example reduces the delay, which improves the UX, but also makes the issues from ZK-4834 happen more often.

Ideally there is no forced delay, and the tree items render as early as possible.