[data grid] autoHeight property affects calculating size of expanded columns #15253
Labels
component: data grid
This is the name of the generic UI component, not the React module!
regression
A bug, but worse
support: premium standard
Support request from a Premium standard plan user. https://mui.com/legal/technical-support-sla/
Steps to reproduce
Link to live example: https://codesandbox.io/p/sandbox/wispy-fire-tn7d4l
Steps:
Basically the issue is that if autoHeight is set to false or not set at all, expanded columns are not able to take the whole available space. Empty space is exactly the same width as summary size of all pinned columns.
Groups affecting first render. If groups are not set then at the beginning columns takes the whole available space, but after resizing empty space appears.
Current behavior
By calling apiRef.current.autosizeColumns({expand: true}), columns are not taking the whole available space
Expected behavior
By calling apiRef.current.autosizeColumns({expand: true}), columns should take the whole available space
Context
The task is to switch between two ways of expanding columns:
Your environment
Used browsers: FireFox, Chrome System: OS: macOS 15.1 Binaries: Node: 22.9.0 - /opt/homebrew/bin/node npm: 10.8.3 - /opt/homebrew/bin/npm pnpm: Not Found Browsers: Chrome: 130.0.6723.92 Edge: Not Found Safari: 18.1 npmPackages: @emotion/react: ^11.10.5 => 11.13.3 @emotion/styled: ^11.10.5 => 11.13.0 @mui/core-downloads-tracker: 5.16.7 @mui/icons-material: ^5.16.7 => 5.16.7 @mui/material: ^5.16.7 => 5.16.7 @mui/private-theming: 5.16.6 @mui/styled-engine: 5.16.6 @mui/system: 5.16.7 @mui/types: 7.2.16 @mui/utils: 5.16.6 @mui/x-data-grid: 7.22.1 @mui/x-data-grid-premium: ^7.14.0 => 7.22.1 @mui/x-data-grid-pro: 7.22.1 @mui/x-date-pickers: ^7.14.0 => 7.22.1 @mui/x-internals: 7.21.0 @mui/x-license: 7.21.0 @types/react: 18.3.12 => 18.3.12 react: 18.3.1 => 18.3.1 react-dom: 18.3.1 => 18.3.1 typescript: 5.5.4 => 5.5.4npx @mui/envinfo
Search keywords: autoHeight datagrid
Order ID: 81026
The text was updated successfully, but these errors were encountered: