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
Currently if we have a page that scrolls and also a virtual data table that scrolls, we have two scrollbars, which is not optimal for user experience.
Proposed solution
A property named "noscrollbar" (or something alike).
If set, the data table will have the total height of the data (calculated by nr. of items and height of the items), but only the records that are within the browser viewport will be rendered.
When the user scrolls the page and other parts of the data table come into view, new items are being rendered.
The text was updated successfully, but these errors were encountered:
Problem to solve
Currently if we have a page that scrolls and also a virtual data table that scrolls, we have two scrollbars, which is not optimal for user experience.
Proposed solution
A property named "noscrollbar" (or something alike).
If set, the data table will have the total height of the data (calculated by nr. of items and height of the items), but only the records that are within the browser viewport will be rendered.
When the user scrolls the page and other parts of the data table come into view, new items are being rendered.
The text was updated successfully, but these errors were encountered: