Not all items are displayed for very long lists (starting with around 1 million items)

[denzakharov]

Not sure if the library was intended to be used with such long lists, but still seems worth mentioning. To reproduce, change item count for official example of FixedSizeList to 1 000 000: https://codesandbox.io/s/github/bvaughn/react-window/tree/master/website/sandboxes/fixed-size-list-vertical?file=/index.js

The last row that is displayed is Row 958697. Locally with different list item I hit a limit of 838860 records. Checked in Chrome and Safari, the result is the same.

[twall]

I don't think it even takes a million elements. I'm using a variable size list, updating item heights as they render, and it only takes a few thousand to make them run off the end.

[vwjh37]

I guess it is caused by the height limitation of elements, I changed the itemSize to some small value, for example 25, then I can scroll whole 1,000,000 rows.
and I find this
https://stackoverflow.com/questions/16637530/whats-the-maximum-pixel-value-of-css-width-and-height-properties

[KeitelDOG]

I'm trying to imagine how much time a person would take to scroll 1M of items in a list without reading them. And if he read even a few of them. Is there use cases for this? Because usually I see search replace the need to scroll more than 1K - 10K.

[AXeL-dev]

Hello @bvaughn, any news for this issue?

[martijnthe]

I'm running into this problem as well.

[bvaughn]

This is not something the library will support. I supported it with react-virtualized (bvaughn/react-virtualized#261) and I later regretted it.

Having thought about this use case a lot over the years– scrolling a 10M pixel list looking for something is not a good user experience. (And because of how virtualization works, in-browser search isn't an option either.) Some sort of pagination/filtering should be used to reduce the list.

I realize this is an opinionated stance, but I think my opinion is at least pretty informed (because I've thought about this a lot over the years).

Thanks for understanding.

[SmartArray]

@bvaughn I am interested in why did you regretted it? I guess it was a use case that just happened to rarely, right?

I am having a use case where I need this, so I am trying to switch back to react-virtualized.
Also, about search functionality, I am considering to use server side search and jump to index X.

Anyway, thanks for all your contributions!