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
Initially brought up this issue in discord but did not get any responses so wanted to increase it's visibility.
When pinning the leftmost column, on Safari the upper left row header cell gets overlapped rows within the table. I have tried debugging this a few times but am not sure why this is occurring. This is ONLY present on Safari, the table acted as expected in Chrome & Firefox
Minimal, Reproducible Example - (Optional, but Recommended)
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.
The text was updated successfully, but these errors were encountered:
@ChristopherBanas its b/c of the rendering of safari ui i am working on it i will let u know. if u don't mind. if you try to make it work anyway and fail
it will give guidance
mantine-react-table version
1.0.0-beta.3
react & react-dom versions
react: v17.0.42, react-dom: v18.0.4
Describe the bug and the steps to reproduce it
Initially brought up this issue in discord but did not get any responses so wanted to increase it's visibility.
When pinning the leftmost column, on Safari the upper left row header cell gets overlapped rows within the table. I have tried debugging this a few times but am not sure why this is occurring. This is ONLY present on Safari, the table acted as expected in Chrome & Firefox
Minimal, Reproducible Example - (Optional, but Recommended)
I have 2 examples
Or by running this small code snippet example
Screenshots or Videos (Optional)
What it looks like in safari
What it looks like in chrome or firefox
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms
The text was updated successfully, but these errors were encountered: