You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a UI where an item animates removal by animating to a height of zero and then removes itself from the list. The bug: Upon removal, if the item is off screen, the list will jump by one item.
Browser: [Chrome, Firefox, Safari, Edge] Testing Safari and Firefox
Version of this package: [x.x.x] 0.29.1
Version of framework: [react, vue, solid-js] [x.x.x] React
Additional context
I am not sure if I am doing something wrong. If there is a better way to implement user-side that will not cause jump without library change, please let me know!
The text was updated successfully, but these errors were encountered:
Currently this library requires shift props to be true if you remove items from the upper outside of viewport. So in this case setting shift: true manually may fix the jump but it will be hard to switch...
Thanks for taking a look! I've thought about this a bit more, and I wonder if #181 could help with this? Because then the item would not be immediately removed by Virtua when off the screen, so Virtua could properly calculate shift when the item is removed.
The only drawback is it would require additional application logic to change append only mode during animation, so maybe there is a more intuitive way...
Describe the bug
I have a UI where an item animates removal by animating to a height of zero and then removes itself from the list. The bug: Upon removal, if the item is off screen, the list will jump by one item.
To Reproduce
#416
Video here: https://github.com/inokawa/virtua/assets/2166114/72cdd3bf-533f-4250-ae91-360161d719ea
Expected behavior
Should not jump by one item.
Platform:
Additional context
I am not sure if I am doing something wrong. If there is a better way to implement user-side that will not cause jump without library change, please let me know!
The text was updated successfully, but these errors were encountered: