react-tabulator
react-tabulator copied to clipboard
bug: Issue on scrolling horizontally with the first column freeze and enable horizontal virtual dom
Title
- bug: Issue on scrolling horizontally with the first column freeze
Environment Details
- react-tabulator version: 0.18.1
- OS: Windows
- Node.js version: v12.8.3
Long Description So I have a huge data set and the horizontal virtual dom seems the perfect feature I need to handle the performance impact. After playing around with it I noticed that it doesn't like to play well with a frozen column since if the column is not frozen it would work just fine.
Here is a codesandbox to showcase the issue, open the project in new window https://codesandbox.io/s/tabulator-virtual-horizontal-freeze-ncoddw
Workaround Looking at the description on the main website, it does say it's experimental and have limitation but it doesn't mention freezing column (unless that's considered column manipulation).
So I removed that feature so I can properly use Tabulator in my project (Please help with a PR if you have a solution. Thanks!)
Frozen columns only became supported with horizontal v-dom on tabulator 5.4 there is an open PR that brings support for 5.3, but we need to update to the latest version to support this feature
Thanks for letting me know, I didn't know that.
From: Richard Welsh @.> Sent: Monday, November 21, 2022 3:00:10 PM To: ngduc/react-tabulator @.> Cc: Franz Buenaventura @.>; Author @.> Subject: Re: [ngduc/react-tabulator] bug: Issue on scrolling horizontally with the first column freeze and enable horizontal virtual dom (Issue #271)
Frozen columns only became supported with horizontal v-dom on tabulator 5.4 there is an open PR that brings support for 5.3, but we need to update to the latest version to support this feature
— Reply to this email directly, view it on GitHubhttps://github.com/ngduc/react-tabulator/issues/271#issuecomment-1321543751, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD3D33HRWZ6JDOCP62PLFD3WJMMXVANCNFSM6AAAAAARKNM2Q4. You are receiving this because you authored the thread.Message ID: @.***>