I've noticed a couple of things when scrolling vertically through our Inspectin DB using Nomad in an Edge Browser:
- The Arrow keys appear to lose their focus. If I click the Down Arrow once, nothing happens... on the 2nd click the View shifts down one Row. That is repeated each time I hit the Down Arrow. It is as if I need to click once for Focus and 2nd time for the Down function... but I'm not moving my pointer off the Down Arrow icon.
- Clicking in the verticle scroll column only advances alternatively 3 or 4 Rows in the View ... 4 the first time, then 3... then 4 etc. Is there a setting that control how many Rows it should advance on each click?
Thx for any help
A1. In a few databases that we tried, we can't recreate this issue. The down arrow only had to be pressed once (not twice). Therefore, we really need a recreateable scenario which generally means a non-GDPR containing nsf that shows the issue for us to debug against (and fix).
A2. We have a collection of scrolling issues to try and improve things. Technical comments:
We are currently limited by the interaction between the browser events and the Nomad code events. The browser cannot express page down/up and as a result, for smaller views, the paging is hardcoded. Home/End and directly dragging the scroll thumb are all workarounds. Keyboard page up/down should work as expected as well.
Coming back to this... the verticle scroll bar is still very inconsistent.
I'd be happy to demo in a Zoom call or create a Case. We have provided a copy of our DB for the Case team to test our issues with and they have quite responsive.
Should I create a case for this issue?
For problem #1, if you have a database with the focus and click issues, please create a case.
For problem #2, I suspect that is related to collapsed views causing the scrolling to be really odd. We have numerous reports of that and have been working on a better fix than the one that went into 1.0.7 but had to be reverted in 1.0.8 because it was worse for too many other scenarios. If you have a database that has this issue and isn't the same database as #1, please add this second database to the case.
Thx Rob, I'll create a case for this issue.
We had provided a DB for testing an issue we had previously with the Horizontal scroll bar, so they should be able to use that to test this issue also. If not I can provide another.