Describe the bug
If your table is wide enough to require horizontal scrolling, and you have specified width numbers for columns, you can get into situations where columns disappear entirely after auto-resizing a column.
To Reproduce
Steps to reproduce the behavior:
- Set up a table that is wide enough to require horizontal scrolling, and has the
width property specified on some columns (Reduced test case: https://codesandbox.io/p/sandbox/recursing-pasteur-dzyc2z)
- Shrink three or more consecutive columns down to their minimum size using the table header drag handles
- Double-click one of the shrunk columns to reset its size to initial
- Notice that two of the shrunk columns have disappeared
Expected behavior
A minimum width should be retained so that columns do not disappear entirely.
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/user-attachments/assets/4dbfc122-a8a5-40bb-8bde-22fa74ee926e
Desktop (please complete the following information):
- OS: Mac OS 26.3.1
- Browser: Chrome 146
- Version: Mantine Core 8.3.18, Mantine Datatable 8.3.13
Additional context
It appears that removing the initial column width resolves this issue; however, I'd still be interested in a resolution or workaround to allow columns to be set to different sizes.
Describe the bug
If your table is wide enough to require horizontal scrolling, and you have specified width numbers for columns, you can get into situations where columns disappear entirely after auto-resizing a column.
To Reproduce
Steps to reproduce the behavior:
widthproperty specified on some columns (Reduced test case: https://codesandbox.io/p/sandbox/recursing-pasteur-dzyc2z)Expected behavior
A minimum width should be retained so that columns do not disappear entirely.
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/user-attachments/assets/4dbfc122-a8a5-40bb-8bde-22fa74ee926e
Desktop (please complete the following information):
Additional context
It appears that removing the initial column width resolves this issue; however, I'd still be interested in a resolution or workaround to allow columns to be set to different sizes.