You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When positionGlobalFilter is set to "left", the search bar displays uneven spacing between the top and left edges due to an additional mx="sm" margin being applied at
Overriding mantineSearchTextInputProps with mx: 0 solves this, but this seems like something that could be fixed as part of the library by using different mx values based on the positionGlobalFilter.
Minimal, Reproducible Example - (Optional, but Recommended)
The bug should be reproducible by simply rendering a table with positionGlobalFilter: "left". If needed, happy to provide a complete reproducible example.
Screenshots or Videos (Optional)
Do you intend to try to help solve this bug with your own PR?
Yes, I think I know how to fix it and will discuss it in the comments of this issue
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.
The text was updated successfully, but these errors were encountered:
mantine-react-table version
2.0.0-beta.7
react & react-dom versions
18.3.1
Describe the bug and the steps to reproduce it
Description
When
positionGlobalFilter
is set to "left", the search bar displays uneven spacing between the top and left edges due to an additionalmx="sm"
margin being applied atmantine-react-table/packages/mantine-react-table/src/components/inputs/MRT_GlobalFilterTextInput.tsx
Line 94 in 36bb1b3
Overriding
mantineSearchTextInputProps
withmx: 0
solves this, but this seems like something that could be fixed as part of the library by using differentmx
values based on thepositionGlobalFilter
.Minimal, Reproducible Example - (Optional, but Recommended)
The bug should be reproducible by simply rendering a table with
positionGlobalFilter: "left"
. If needed, happy to provide a complete reproducible example.Screenshots or Videos (Optional)
Do you intend to try to help solve this bug with your own PR?
Yes, I think I know how to fix it and will discuss it in the comments of this issue
Terms
The text was updated successfully, but these errors were encountered: