Damian Pieczynski
Damian Pieczynski
@MatchuPitchu That's interesting! It seems like something might have changed in Chrome recently. When I tested will-change: transform before, I didn’t notice much difference, but I’ll look into it again....
@MatchuPitchu directly on each item.
@soliyapintu @vansh3476 @wwesolowski just to be on same page, basic combining react-table with react-virtual everyone experiencing these problems?
@mio-moto Wow, great work! Thanks for this detailed summary. Do you maybe have some ideas on how we can get some reliable numbers to test the performance and have something...
@pr-o can you check the CI error
Hi, yes it's know issue as the RO callback will be called when changing display. One option could be to pass custom measureElement that will skip those updates ```tsx const...
> Also, example with custom measureElement, doesn't do a thing. Ooo sorry you are right, before it was working, need to check it.
Other option would be to skip updates of RO, something like this ```tsx const updateSizeRef = useLatestRef(updateSize ?? true) const virtualizer = useVirtualizer({ measureElement: (element, entry, instance) => { if...
@samstronghammer most cases this error has no real effect, other than log in console what is annoying. Wrapping it with requestAnimationFrame would creates it's own issues.
Thanks for sharing more details, and I totally understand the impact this has on your workflow. I’ll try to debug the issue further and see if I can provide a...