Open hansanghoon opened 7 years ago
I just noticed this myself, and was about to write up an issue, until I saw yours. I dug in a little using the React extension for Chrome developer tools. Things I noticed:
So this does look suspiciously like a limit in the browser. But where and why? I have no idea.
macOS 10.12.4 Google Chrome Version 57.0.2987.133 (64-bit)
Problem is worse than I thought.
In FireFox the last index to render properly is 178956, with offsetTop 8947800 or 0x888858 in hex The next one isn't stacked on top of the others, like it is in Chrome, but it just doesn't display. It's index 178957, offsetTop 8947850 or 0x88888A in hex.
I believe this issue has been resolved in FDT2 if you'd like to check. @KamranAsif may be able to give details on the way it was resolved.
Yes, this is fixed in Fixed-Data-Table-2. I was just discovering that the problem was the incredibly large values going into CSS transform, which really didn't need to be done that way. Glad to know that there is a new project.
When I found Fixed-Data-Table, I thought I was at the right place. I didn't see any big red "DEPRECATED" warnings, or links to FDT2. Oh well.
Thanks for linking me to where I needed to go.
Ya unfortunately Facebook has yet to deprecate this repo in-spite of the inactivity. They also softly encourage React-Virtualized over the fork of this as it provides a more general solution for those willing to switch over. In the meantime we're working on hyper optimized performance specifically for interactive grids over on FDT2 and will continue to do so for anyone who has FDT issues.
More discussion on deprecating this repo can be found on #468 and #408
https://facebook.github.io/fixed-data-table/example-object-data.html
markup of last visible row
and first of invisible row
looks like its position exceed browser limitation.
macOS 10.12.4 Google Chrome Version 57.0.2987.133 (64-bit)