You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be highly beneficial to allow more control over the enableVirtualization option. Currently, enabling virtualization affects both rows and columns automatically. However, it would be great to have the ability to specify the scope of virtualization, such as rows, columns, or all, instead of just a simple true/false toggle.
This feature could also address the issue with frozen columns on the right (#2873), enabling the freezing of columns through CSS alone. Now, applying a CSS-based solution conflicts with virtualization, as enabling it prevents the last column from rendering correctly, thereby breaking the freezing behaviour.
Proposed Solution
The proposal is straightforward: allow the enableVirtualization option to accept something like columns | rows | all as value, and adjust the behaviour accordingly. This would provide more flexibility in configuring virtualization while addressing current limitations.
The text was updated successfully, but these errors were encountered:
Use Case
It would be highly beneficial to allow more control over the
enableVirtualization
option. Currently, enabling virtualization affects both rows and columns automatically. However, it would be great to have the ability to specify the scope of virtualization, such as rows, columns, or all, instead of just a simple true/false toggle.This feature could also address the issue with frozen columns on the right (#2873), enabling the freezing of columns through CSS alone. Now, applying a CSS-based solution conflicts with virtualization, as enabling it prevents the last column from rendering correctly, thereby breaking the freezing behaviour.
Proposed Solution
The proposal is straightforward: allow the
enableVirtualization
option to accept something likecolumns | rows | all
as value, and adjust the behaviour accordingly. This would provide more flexibility in configuring virtualization while addressing current limitations.The text was updated successfully, but these errors were encountered: