You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an issue but a question. When responsive plugin is used and DataTable has sorting columns activated, the columns that are collapsed to the child rows cannot be clicked on to re-sort the data table by those columns. Any suggestions on how to deal with this? The idea is to give the users access to sort by all columns and not only by the un-collapsed columns they see when responsive layout is activated by the user (either by zooming in or using mobile browsers). I was thinking that maybe have a dropdown box before DataTable with search options that list all of the columns that can be used for sorting, but not sure if that would be possible to do or not?
The text was updated successfully, but these errors were encountered:
I was thinking that maybe have a dropdown box before DataTable with search options that list all of the columns that can be used for sorting, but not sure if that would be possible to do or not?
I think that's a good option and one that I should look at adding as a core part of the Buttons. I've made a note of that in my tracker. It is certainly possible, and would be similar to the column visibility button.
Not an issue but a question. When responsive plugin is used and DataTable has sorting columns activated, the columns that are collapsed to the child rows cannot be clicked on to re-sort the data table by those columns. Any suggestions on how to deal with this? The idea is to give the users access to sort by all columns and not only by the un-collapsed columns they see when responsive layout is activated by the user (either by zooming in or using mobile browsers). I was thinking that maybe have a dropdown box before DataTable with search options that list all of the columns that can be used for sorting, but not sure if that would be possible to do or not?
The text was updated successfully, but these errors were encountered: