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
While pinning columns to the right, pinned column menu item gets pushed to the bottom of the menu, which is kinda unpleasant as it doesn't happen to the column items pinned to the left(they keep their position in menu order).
Screen.Recording.2024-02-29.at.09.45.58.mov
Minimal, Reproducible Example - (Optional, but Recommended)
Try it on any pinning example.
Screenshots or Videos (Optional)
Proposed solution
Screen.Recording.2024-02-29.at.09.46.34.mov
Do you intend to try to help solve this bug with your own PR?
Yes, I am also opening a PR that solves the problem along side 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:
From my perspective, the current implementation in v3 may feel a bit inconvenient for users due to the "jumping" of items. However, the menu now provides a clearer representation of the structure within the table.
I would suggest keeping the current implementation. Could you share your thoughts on this and perhaps close the issue, @renatoka?
material-react-table version
v2.12.1
react & react-dom versions
18.2.60 && @18.2.0
Describe the bug and the steps to reproduce it
While pinning columns to the right, pinned column menu item gets pushed to the bottom of the menu, which is kinda unpleasant as it doesn't happen to the column items pinned to the left(they keep their position in menu order).
Screen.Recording.2024-02-29.at.09.45.58.mov
Minimal, Reproducible Example - (Optional, but Recommended)
Try it on any pinning example.
Screenshots or Videos (Optional)
Proposed solution
Screen.Recording.2024-02-29.at.09.46.34.mov
Do you intend to try to help solve this bug with your own PR?
Yes, I am also opening a PR that solves the problem along side this issue
Terms
The text was updated successfully, but these errors were encountered: