virtual
virtual copied to clipboard
Scrolling up on mobile/trackpad resets position using Dynamic and Vue
Edit
As described here, this is a working true fix https://github.com/TanStack/virtual/issues/619#issuecomment-1969516091
Describe the bug
This problem occurs when you use smooth scrolling, i.e. via touch screen or trackpad
Using the 'dynamic' version of the scroller and Vue problems occur when you scroll up. Other versions, such as fixed an variable height work fine.
Scrolling down works fine, however, the second you start scrolling up it causes a jittery movement and the rows don't actually scroll up, instead it resets its position. You can hopefully see it clearly in my provided videos. For example: row 53 stays in view.
The problem is most notable by scrolling slowly. By scrolling really fast you can get over it temporarily, but as soon as the scroll starts slowing down, the problem occurs.
This issue occurs in the offical example!
Your minimal, reproducible example
https://ryhp23-3001.csb.app/
Steps to reproduce
- Open on mobile or switch the mobile emulation mode using the devtools
- swipe down in the list, this works fine
- Swipe up, position keeps resetting
Expected behavior
I expect to be able to smoothly scroll up using the dynamic variant on all platforms.
How often does this bug happen?
Every time
Screenshots or Videos
https://github.com/TanStack/virtual/assets/22410563/75e62c13-91d8-4987-9242-73b217739108
Platform
Problem occurs on: Chromium on MacOS Firefox on MacOS Chrome on Android Firefox on Android Firefox on Windows Edge on Windows
Problem does NOT occur on: Webkit based browsers basically: safari on iPhone (emulator) safari/Chromium/Firefox iPad Safari on MacOS
tanstack-virtual version
3.0.0-beta.68
TypeScript version
4.8.4
Additional context
The bug does not exist on the React wrapper of virtual.
Terms & Code of Conduct
- [X] I agree to follow this project's Code of Conduct
- [X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
A backport for the current stable was discussed. It would be great if that happened.
There is no plans to do backports to stable as the stable branch isn't supported upstream, but we've done two releases since this point based on the main branch, so you should be able to pick up 3.3.0, or 3.4.0 to get this fix. Thanks!