Replies: 1 comment
-
|
Thanks for the clear explanation! virtualization="auto" | "on" | "off"
virtualizationThreshold={number}This will let you disable it for small objects or specific views, or force it on for large trees. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I wanted to put in a request for some improved control over how we handle virtualization in our components.
Right now, the default behavior can be a little rigid, and I think giving developers more options here would really help with performance and user experience, especially when navigating between short and long objects.
A Simple On/Off Switch: We would benefit from a simple way to turn virtualization completely off when necessary.
For super short lists, the overhead of running the virtualization engine isn't worth it. And for things like printing or global searching, we often need all the elements to be rendered non-virtually. A simple isVirtualizationEnabled: false property would solve this cleanly.
Let me know what you think about prioritizing this! It feels like a key factor for polished performance in our data-heavy views.
Beta Was this translation helpful? Give feedback.
All reactions