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
I am currently facing challenges in setting appropriate widths for my multi-column tables. Despite numerous adjustments, I am not yet satisfied with the outcomes. My goal is to ensure that all column headers are clearly visible and that the widths are optimally suited for the content in each column. I have attempted to set a fixed table width and have sought advice from discussions on Stack Overflow, but the solutions have not been effective for my specific dataset.
So.. unfortunately this is an inherent limitation of how reactable works, and it's not possible to automatically set column widths based on content. The best you can do for now is play with the minWidth column settings, make the table resizable for users, and/or condense columns.
In the future, it could be possible for reactable to eventually support automatic column widths based on content, like you'd expect from a standard HTML table. That would require significant changes to the library though.
And just generally, fitting lots of column information in a single-page readable table is just a tricky task. You might also consider design-level changes like merging multiple columns. An example of this would be in the Popular Movies demo, https://glin.github.io/reactable/articles/popular-movies/popular-movies.html
Dear @glin ,
I am currently facing challenges in setting appropriate widths for my multi-column tables. Despite numerous adjustments, I am not yet satisfied with the outcomes. My goal is to ensure that all column headers are clearly visible and that the widths are optimally suited for the content in each column. I have attempted to set a fixed table width and have sought advice from discussions on Stack Overflow, but the solutions have not been effective for my specific dataset.
Best,
Shixiang
The text was updated successfully, but these errors were encountered: