Scrolling up with the 'up' arrow key does not work.
See original GitHub issueI’m submitting a … (check one with “x”)
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter
Current behavior
- Create a ngx-datatable with the scrollbarV property, focus on the table and use the arrow keys to scroll down.
- Try to scroll back up using the arrow keys and you can’t.
Expected behavior
Using the arrow keys should allow you to scroll back up the table.
Reproduction of the problem
- Visit http://swimlane.github.io/ngx-datatable/#virtual-scroll focus on the table and use the arrow keys to scroll down.
- Try to scroll back up using the arrow keys and you can’t.
What is the motivation / use case for changing the behavior?
Accessibility
Please tell us about your environment:
MacOS Sierra (Also tried on Ubuntu 14.04) Chrome
-
Table version: 9.3.0
-
Angular version: 4.1.3
-
Browser: Only tested in Chrome
-
Language: All
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:19 (9 by maintainers)
Top Results From Across the Web
Cant scroll, Arrow keys not working in Chrome browser
Fix Cant scroll, Arrow keys not working in Chrome browser · 1] Restart the computer and browser · 2] Disable Caret Browsing ·...
Read more >My arrow keys will not scroll down when I hold them down
On a Windows PC, to turn scroll lock on and off, press the Scroll Lock Key. It's typically above the arrow keys, or...
Read more >up key not working and down arrow key scrolling on its own
Go to settings > update and security > troubleshoot > additional troubleshooters > keyboard > run troubleshooter. Restart the computer and see ...
Read more >Why can't I use the arrow keys to scroll up and down websites ...
I assume it's because of this glitch (assuming) that when I go to press the up or down arrow keys it no longer...
Read more >[Fix] Arrow Keys Not Scrolling Webpages, Navigating Through ...
1. Open Google Chrome web browser, click on 3-dots menu (Main Menu) and select Settings option. · 2. It'll open Chrome Settings page....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@amcdnl I’m a one man shop here and rather new to opensource and typescript/angular in general. I’m not sure if I have a gitter account, but I will signup for one if I don’t. I worked real hard to not break anything with onpush. I do a lot of ngOnCheck and perform my own change detection. I forgot to mention, but I added a mode for change detection on the table (‘manual’ and ‘auto’), and it helps with the live demo. I set it to manual for better performance when I’m not dealing with live row data. I probably know your codebase really well now, along with parts of the angular 2/4 framework trying to fix major performance issues I was having the last 6 months.
My codebase is all broken at the moment, doing a lot of refactoring, but if you would like to check out an older commit, I can publish it, otherwise, I hope to be public in a week or so.
@amcdnl It’s rather big and it’s a decent breaking change at the API level. I forked it to add the following features (mostly for perf issues I was having):
@Input()
. It was impossible to reason about how changing one input property would affect the rest of the library. Also, there was a back and forth flow of data from thebody
to thedatatable
, making some things highly difficult to test.focus()
is called, triggeringupdateIndexes()
, etc.These changes change how some of the demos work, especially when using functions that rely on
$$index
. I originally tried to make my changes in small bite size chunks, but some of the things I needed for my own project needed some fundamental changes, and while I was at it, I made some more bigger changes so that I could reason better about the code base. I figured the change is way too big to merge, but once I share my results, you are welcome to break it up into smaller pieces, if possible. I’m not really sure how that PR would go if I attempt it.