swimlane
Scroll does not work properly on the datatable. Workaround: Keep the mouse pointer on the scroll bar
I'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
When scrolling on the data table a lot of scroll events are lost. This is causing the scroll to look very laggy. This is also reproducing on the official examples of ngx-datatables: https://swimlane.github.io/ngx-datatable/#horz-vert-scrolling The scroll works as expected when the mouse pointer is on the scroll bar zone
Expected behavior
The scroll should work smoothly on the data table.
Reproduction of the problem
Create a data table with vertical scroll bar. Try to scroll through the items in the table. Our problem is reproduced on a custom data table (infinite scroll) but this issue can be also reproduced on official examples.
NOTE: This issue started reproducing after upgrading chrome/edge to the latest version
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Windows 10
- Table version: 17.1.0
- Angular version: 10
- Browser: Google Chrome Version 102.0.5005.115 (Official Build) (64-bit) Microsoft Edge Version 102.0.1245.41 (Official build) (64-bit)
- Language: [all | TypeScript X.X | ES6/7 | ES5]
@MitranLiviuMarian Could you please add a comment once you manage to figure out a reasonable workaround? We're affected by issue too, and we're actively investigating what exactly causes the problem, and how it could be fixed. Thanks!
@MitranLiviuMarian As far as I tested, applying the styling transform: translateZ(0) to datatable-body solves the problem.
Still, I haven't been able to figure out why it happened in the first place, so in case you manage to come up with an explanation, I'd be curious to also understand it.
For those who still face the issue/want to investigate it, we've found out that this happens only in Chromium. In Firefox no problems appear. Also, in Chromium 102 the error was more prominent and appeared much more frequently than in Chromium 101. Other Chromium versions weren't tested.
Hello Daniel,
Thank you very much for your workaround! Works great now ! Until now I was not able find the root cause of this issue.
Best regards, Marian