Closed sanketjo96 closed 4 years ago
Hey Marc - did you get chance to go over this ?
Hey. Not yet sorry. I'm back at work on Monday so should have some time then
On Fri, 27 Dec 2019, 08:32 sanketjo96, notifications@github.com wrote:
Hey Marc - did you get chance to go over this ?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/marchaos/react-virtualized-sticky-tree/issues/15?email_source=notifications&email_token=AAVBY6LM3KUA2W6DKUA3IR3Q2W4RPA5CNFSM4J6WWIR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHWZ5WY#issuecomment-569220827, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVBY6IF5RLZLUUAHXVH7ETQ2W4RPANCNFSM4J6WWIRQ .
Did you get a chance to have a look marc ?
Hey @sanketjo96. Thanks for the sandbox - I can see that node 8 is actually removed from the dom, so should be easy find out what's going on.
Thanks for reply. Could you please let me know if/when you are planning on fix ?
Hey @sanketjo96. I haved fixed this in branch issue_15. Just sorting out a release.
I've pushed a new version. Can you try 2.1.26 ? https://codesandbox.io/s/xenodochial-wu-feq0t?from-embed
Thanks Marc for fix. Wll try out with new version and will notify here. Thanks a lot again
Hey Marc, I am done with initial round of testing and found a bit different issue. I am unable to scroll back up using scrollNodeIntoView
Please have a look at - Sandbox
This worked well when I synced lib back to 2.1.25
Can you please have a look ? I guess we are always returning early when we reach to max scroll position. May be we need to consider the case when user wanted to scroll back up.
Hey. Yes, will take a look. If you can, I'll get a branch for you to test before releasing.
Yes. That will make it safe. Thanks for quick response.
Hey - Please share the branch once you commit the change. Thanks.
See comments in other issue - looks to be border related.
Came across the weird case where calling scrollNodeIntoView after manual scrolling hides row randomly. The row gets rendered again when scroll.
Created a below reduce test case to showcase the issue - Sandbox - reduce test case
This looks strange. One observation though, if you increase the overscanRowCount to say 20 (in above case) it stops. Could you please have a look here ?.
I will update if i see any unusual thing.