-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[data grid] FilterPanel column select menu is not customizable #5102
Comments
You can change to use the non-native select with <DataGrid componentsProps={{ baseSelect: { native: false } }} /> Note that it will change all selects. You can also pass a custom component to Which styles do you want to apply? Do the CSS classes are not sufficient? |
Thanks, that's it. |
The filter panel uses the ClickAwayListener. By default, this component doesn't work with the non-native Select (mui/material-ui#25578). In #4361, we enabled an option that allowed to use the non-native variant. In v6 we may want to make this the default behavior. |
It would be nice to add it to the v6 issue if we do want to make this the default behavior. |
The current list of columns seems to list all available columns, including hidden ones. In our organization, we have a page which uses the DataGridPremium, with 87 available columns. Most of which are hidden by default. Overriding the entire |
This has been a problem for our organization as well. From all of my tinkering and looking into this, I think the only option is to create a custom filter panel. Our list is huge and we want an autocomplete so we can filter it as well as add the list item component for the menu to allow for subtitles. It is extremely strange to me that it is not customizable as most mui items allow for different components to be passed in as props to override stuff. |
Duplicates
Latest version
Current behavior 😯
It is not possible customize FilterPanel column select menu because native select is used as component.
Expected behavior 🤔
Posibility set styles via componentProps: { filterFormProps: { columnInputProps: .....} } , or possibility use custom component.
Steps to reproduce 🕹
Steps:
Context 🔦
No response
Your environment 🌎
`npx @mui/envinfo`
Order ID 💳 (optional)
No response
The text was updated successfully, but these errors were encountered: