-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DataGrid] Implement Column groups #295
Comments
@mchelen Thanks for the feedback. It's not supported with the |
As a workaround, you can do <TableRow>
{columns.map(column => (
<TableCell
key={column.id}
align={column.align}
- style={{ minWidth: column.minWidth }}
+ style={{ minWidth: column.minWidth, top: 57 }}
> |
Thanks, that's what we did but when scrolling the second header row overwrites the first one. |
@mchelen Can you reproduce this issue with the codesandbox I have provided in my previous comment? |
Oh cool, yeah that works! I was looking at your sandbox and that change wasn't saved there. Here it is with the change: https://codesandbox.io/s/material-demo-r1p51 |
Moving to #195 |
Why is this issue title prefixed with |
The fixed header option in https://material-ui.com/components/tables/#fixed-header is not compatible with multiple header rows from this example https://github.com/mui-org/material-ui/blob/master/docs/src/pages/components/tables/SpanningTable.js
Current Behavior 😯
The second header row is sticky, but not the first.
Expected Behavior 🤔
Both first and second header row should be sticky.
Steps to Reproduce 🕹
Steps:
<Table>
withstickyHeader
prop (reference: https://material-ui.com/components/tables/#fixed-header )<TableRow>
inside<TableHead>
(reference: https://github.com/mui-org/material-ui/blob/master/docs/src/pages/components/tables/SpanningTable.js )<TableRow>
content will replace firsthttps://codesandbox.io/s/material-demo-vo8qp
Context 🔦
We want to display a table with multiple header rows, and have all those rows be fixed "sticky" when scrolling.
Your Environment 🌎
The text was updated successfully, but these errors were encountered: