As can be seen below in the GIF capture, after I clicked on the Edit button, all the columns started to resize themselves like crazy. It was because I toggled the showSelectionColumn prop in TableSelection plugin.

From below capture GIF, you can see that there is a transform: translateX() appearing in in the style tag.

The columns should not resize themselves drastically like crazy.
In my code, I have SelectionState and TableSelection as the grid plugins. In TableSelection, I toggle the showSelectionColumn according to my state. Quite often, after I press the button to change the state (thus toggling the visibility of the selection column), the size of other columns started to auto-resize wildly and drastically, as shown in my screen capture GIF. This is very annoying.
I expect there to be a config where I can disable the column resizing animation entirely. i.e., I should be able to disable the entire transition: translateX() thingy. I understand that the animation under some circumstances are desirable, but in my case, I would like them to be disabled because they are causing much bigger problems.
This is my temp fix now, but I'm still looking for a better way to do it.
gridContainer: {
width: '100%',
['& td']: {
transform: 'none !important'
},
['& th']: {
transform: 'none !important'
}
},
Hi,
We know about this problem and the fix you described is the most appropriate for the moment. We will discuss how to better resolve this issue in the future.
This also happens on showing/hiding columns using column chooser if the grid has a lot of columns.
Has this not been fixed yet? We just encountered this bug as well.
Hi, I'm faced the same issue when use Grouping feature with CustomSummary, after ungrouping any column.
@franklixuefei how/where are you applying those styles?
Hi all
聽
This error may refer to the defaultColumnWidths option of the TableColumnResizing plugin. In this option, you need to specify a number type, not a string type.
Here is an example where this error is reproduced. In the second example, everything work correctly.
Please let us know if this solution suits you.
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests.
Most helpful comment
Hi,
We know about this problem and the fix you described is the most appropriate for the moment. We will discuss how to better resolve this issue in the future.