weird behavior when using 'rangeExtractor' to make a colum sticky #917
Unanswered
ps-selliott
asked this question in
Q&A
Replies: 1 comment 3 replies
-
I am seeing the same issue, using this example with rangeExtractor |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I'm currently trying to implement a virtualized table using
@tanstack/react-table
where the first column is sticky. This has proven to be more challenging than I thought, as I'm experiencing some unexplainable behavior when usingrangeExtractor
to force the "visible range" to always contain0
(first col) as its first index.In my example below, I made some small modifications to the existing Tanstack example for column virtualization. While this example does not show the sticky column behavior, it does show the aforementioned weird behavior where columns seem to stop rendering once the virtualization kicks in.
Minimum Reproduceable Example
https://codesandbox.io/p/devbox/great-phoebe-slhtxc
Perhaps by forcing the rendering of the first column, maybe that is messing with the virtualizer's state in some way?
Reading rangeExtractor in the developer docs, it specifically says it can be used to add/remove items...useful for sticky items, etc. so I'm fairly confident I'm at least on the right track to finding a solution.
If anyone has any insight into this issue I would be most appreciative.
Beta Was this translation helpful? Give feedback.
All reactions