-
-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tabulator row selection does not persist when changing pages #4367
Comments
Thanks @CrashLandonB. Agree that this may be nice however we intentionally did not implement this as relying on it seems somewhat error prone. Basically my concern here is that selections reset if you don't press |
@philippjfr Interesting point about the In my head, I was equating the But to your question, I'd say I've also realized that even if I made my selections, I don't see a means to filter the table to "selected rows", right? I definitely want to do this, so my best approach might be to simply give the users that extra "selected" column, let them manually change that value, and then use the header filtering to let the user collapse it to selected rows. |
Very good good point, I had forgotten about the checkbox selection feature. That does change my perspective and means we should absolutely persist selections across pages. On the filtering questions we can brainstorm separately. Certainly you could add your own toggle to temporarily switch out the data to display only selected data. |
Sounds good. I think I have an alternate approach with Tabulator to get the job done, but I'll certainly look forward to seeing the change if you proceed. Thanks! |
Could you share the alternate approach ? I just encounter the same question as you now~ |
MRE:
With the example above, if I select a few rows, change pages, select a few more rows, and return to the original page, I don’t see the rows selected any longer.
The MRE above seems to recreate the issue with 300 rows. I intend to use this on a data set with around 100,000 rows.
(FYI, relevant conversation and confirmation that others have seen the issue available here)
The text was updated successfully, but these errors were encountered: