-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overscan in px, instead of # of items #378
Comments
Hi, overscan with px sounds nice! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
In my application, I find myself tweaking overscan depending on item height. I believe that overscan being the # of items to load off screen is limiting in the following ways:
Describe the solution you'd like
Overscan =
px
of items to load off screen.For example, if overscan = 500, then Virtua will load at least 500px of items off the edge of the screen.
This resolves both of my above scenarios.
Describe alternatives you've considered
Adjusting overscan for item size works for problem one but not two.
Additional context
react-virtuoso has this, except it's called
increaseViewportBy
.See: https://virtuoso.dev/virtuoso-api-reference/
This may render #298 unnecessary, since if it was defined it could just be a static number like
200
px or something.The text was updated successfully, but these errors were encountered: