Up and down arrows not working in chrome

UP AND DOWN ARROWS NOT WORKING IN CHROME UPDATE

Allow using keyboard keys to scroll up and down with the virtual scroller by using a service instead of over estimating the bottom scroller and only by accident scrolling when the system scrolls after focus() is called, triggering updateIndexes(), etc.

I'm currently in the process of making the scroller generic so I can add horizontal virtual scrolling as well.

Making the scrollbar virtual, allows me to add things like animated scrollbar (collapsing, shrinking, and removing the buttons when not in use like done on some scrollers).

Without virtualization, not allowing it to scroll till after it's rendered (currently impossible since the scroll event occurs after scrolling but before it's actually rendered, requiring it to play catch up with the virtual scroller).

Virtualizing the scrollbar itself to fix the perceived click and drag scrolling performance that showed whitespace during moving the scroll bar on IE/Edge.

Also, there was a back and forth flow of data from the body to the datatable, making some things highly difficult to test.

Restructured the flow of properties to use services or separate classes instead of pass though the component It was impossible to reason about how changing one input property would affect the rest of the library.

Added types and generics and removed almost all any.

Made everything OnPush change detection internally.

UP AND DOWN ARROWS NOT WORKING IN CHROME UPDATE

Added special update zones for scroll and page events to prevent global change detection.Separated $$index, $$expanded from the rows source (created mappings).I forked it to add the following features (mostly for perf issues I was having): I added quite a lot of changes that are major breaking changes, that are needed to support things like immutable data source, that is currently not possible with this library as it is embedded fields like $$index directly in the source It's rather big and it's a decent breaking change at the API level. My goal is to bring all my changes back if they will be accepted. I will be sharing my fork shortly, so anyone can see how I made it work. I had to create a service that keeps track of what item is focused and scroll just enough for the next item to be drawn, then in a callback, after the scroll occurs, get the next item that was selected and focus it. I got it working on my forked copy but I made a significant amount of changes from this repo. It will take a lot of work to enable this properly on the current version. TLDR - An easy fix would be to create another bug on the top to over draw it by one row as well, but that's not ideal.

The library calls focus() which triggers a scroll to bring it inside the view, thus triggering more items below it to be drawn (due to a bug, it adds items slightly below the view window) making it appear that you are actually scrolling using the arrow keys, but that bug only over draws on the bottom half, the top half does not have the bug.

If you resize your window so the last visible item is near the bottom of the list, pressing keydown will not trigger the next items to be drawn, it's an accidental artifact of the system that it's even possible. I figured out what the issue is and why you are having and why I wasn't able to replicate it.

Up and down arrows not working in chrome