column filter (select) input padding

[drmax24]

material-react-table version

2.13.2

react & react-dom versions

18.0.20

Describe the bug and the steps to reproduce it

if i add InputProps to my column filter which is a select dropdown
clear button (X) disappears
even if i have sx empty it still disappears.

What I try to achieve is to give a little more space for select option text in a narrow column. Ie at this moment most of the space inside select are used by right input padding (24px) and ellipses... ~20 px. and for my letters it uses only around 20 px displaying 2 letters while there is space for at least 6

        {
            accessorKey: "role",
            header: "Rolle",
            enableSorting: false,
            size: 120,
            filterSelectOptions: Object.values(RoleFilterUserOptsEnum),
            filterVariant: "select",
            muiFilterTextFieldProps: {
                placeholder: "Filter",
                sx: {
                    width: "100px",
                },
                InputProps: {
                    sx: {
                        padding: "0px 0px",
                    },
                },
            },
        },

Minimal, Reproducible Example - (Optional, but Recommended)

        {
            accessorKey: "role",
            header: "Rolle",
            enableSorting: false,
            size: 120,
            filterSelectOptions: Object.values(RoleFilterUserOptsEnum),
            filterVariant: "select",
            muiFilterTextFieldProps: {
                placeholder: "Filter",
                sx: {
                    width: "100px",
                },
                InputProps: {
                    sx: {
                        padding: "0px 0px",
                    },
                },
            },
        },

if I set InputProps X just disappears

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

No, because I do not know how

Terms

• I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.