-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Virtual Scrolling stalls when scrolling via keyboard with large set of complex data #14765
Comments
I am able to reproduce this. It seems like maybe the element that was clicked on originally is destroyed and then the scrolling stalls. Clicking inside the viewport again will make it work again |
Any ideas or workaround ? |
Having the same problem. Any progress on this? Reproduced in Chrome 80.0.3987.122 (Official Build) (64-bit)
|
I ended up rewriting a part of the virtual scrolling lib into what I was working on at the time. I don't remember which changes I made exactly, but they are in this directory -> s73obrien/ngx-hex-input/projects/ngx-hex-input/src/lib/scrolling |
Workround for me: Don't click into the viewport, e.g. a table. Instead, click on the scrollbar. As long as the scrollbar has focus you can use down/page down and up/page up without issues. |
Bug, feature request, or proposal: Bug
What is the expected behavior?
When scrolling down the list by holding down the up or down arrow key, the list should scroll smoothly all the way down to the end
What is the current behavior?
When scrolling down the list by holding down the up or down arrow key, at random times and seemingly random circumstances, the scrolling behavior stalls. I believe the focus is being lost on the list for whatever reason as, if you click on the list and press the arrow key, scrolling resumes as normal.
What are the steps to reproduce?
StackBlitz here. Click on the list and press and hold the down arrow key. It may take a couple attempts, but eventually it should stall.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Reproduced in Chrome 71.0.3578.98 and IE 11. Could not reproduce in Firefox 64.0.
Is there anything else we should know?
Resource-bound maybe?
The text was updated successfully, but these errors were encountered: