Closed syllith closed 2 years ago
@syllith seems like chrome issue... needs some investigation
Interesting issue...seems like I found the reason. New FAQs page
If you just use List or Table components - you just need to upgrade the library. All new styles are added automatically. I have also removed style.css file in new versions (check documentation to see all changes)
Great, thank you for the swift response. I'm redoing my project in typescript on React 18. I'm getting errors installing due to peer dependencies. Am I safe to install with --legacy-peer-deps? Are you considering updating your package to be fully compatible with React 18?
Added react 18 support. Please upgrade
You are incredibly quick, thank you so much. I'm currently reconstructing the list portion of my project, I will let you know if there are any problems. Thank you again!
Everything is working perfectly. Thank you again, you're amazing. Closing the issue now since you've addressed it perfectly. Keep up the good work. This truly is an amazing package you've made!
Oh hey, side note, did you happen to fix a problem when scrolling manually with the mouse on the scroll bar? The scroll bar position used to get unaligned with the mouse when scrolling very quickly, but it looks to be resolved?
Yes, I have this issue on React 18, will investigate this problem. Could you please start new issues in future?)
Of course. I'm sorry. For some reason it seemed to be working yesterday, but now that I've rechecked, the problem still seems to be there. I will start a new issue about it now, just so it's official
Hey bud, hope all is well. The list has been working great since you addressed those issues a while back. I'm having a little problem now that my team recently brought to my attention and it seems to be with the package itself, as it's happening on your sample site as well.
The problem is, on Chrome only, when scrolling WITHOUT moving your mouse, scrolling completely stops until the mouse is moved again. I've attached a video that attempts to demonstrate this, but you might need to try it yourself to fully understand the problem.
I don't ever recall this being an issue, and my suspicion is that the new Chrome version 100 that came out might be the source of the problem. I feel I would have remember that being an issue in the past and would have brought it to your attention sooner. If you could please look into this, that would be fantastic. Thank you
!