Here’s a professional and concise feedback message you can use to address the issue of nestedRows not supporting virtualization in Handsontable

Tags: #<Tag:0x00007f51c1cafed0> #<Tag:0x00007f51c1caf9f8>
#1

Dear Handsontable Team,

I hope this message finds you well. I am writing to provide feedback regarding the nestedRows feature in Handsontable. While the feature is incredibly useful for displaying hierarchical data, I have noticed that it does not support virtualization (virtual scrolling).

In scenarios with large datasets, the absence of virtualization can lead to performance issues, as the entire dataset is rendered in the DOM, causing slowdowns and impacting user experience. Virtualization is a critical optimization for handling large amounts of data efficiently, and its absence in nestedRows limits the feature’s usability in performance-sensitive applications.

I would like to kindly request the addition of virtualization support for nestedRows in future updates. This enhancement would significantly improve the performance and scalability of Handsontable when working with hierarchical data structures.

Thank you for your attention to this matter. I appreciate your continued efforts to make Handsontable a powerful and versatile tool for developers. Please let me know if there are any updates or plans regarding this feature.

#2

Hi @AexFreedom

Virtualization also works for nestedRows. You can test it at https://jsfiddle.net/rqwca2ek/.

53
Zrzut ekranu 2025-02-17 o 08.46.53.png1031×1173 159 KB

When we load the example we can see row index 22 as the last one in the DOM. Then when you scroll to the bottom we have new rows added

33
Zrzut ekranu 2025-02-17 o 08.46.33.png1034×1168 166 KB

And the top rows are also removed from the DOM, and the first visible TR element has index 8. (that may depends on your system scale and browser zoom).

#3

Thank you for your reply! I found the issue: when I set preventOverflow: "horizontal" , the Virtualization stops working. This might be a bug. By the way, I’m using handsontable/vue.

#4

Yes, preventOverflow seems to alter that behavior in an unexpected way. Thank you for sharing. I will investigate that subject further in the end if the week (now we are preparing to release Handsontable v15.1.0).