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
will stick the columns to the right instead of the left because of RTL direction
It would be nice if we were able to change physical, directional properties/options like left or right options to logical properties/options like start and end
Also, these functions are not RTL-friendly too
column.getStart("left/right")
column.getAfter("left/right")
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
Do you intend to try to help solve this bug with your own PR?
Maybe, I'll investigate and start debugging
Terms & Code of Conduct
I agree to follow this project's Code of Conduct
I understand that if my bug cannot be reliable 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:
TanStack Table version
v8.21.2/v9.0.0-alpha.10
Framework/Library version
React v19.1.0
Describe the bug and the steps to reproduce it
Hi π
First of all, thanks for the TanStack packages β€
I have some issues with columns pinning in RTL documents, it seems like the column pinning options are not RTL-friendly
For example, this option
will stick the columns to the
right
instead of theleft
because of RTL directionIt would be nice if we were able to change physical, directional properties/options like
left
orright
options to logical properties/options likestart
andend
Also, these functions are not RTL-friendly too
column.getStart("left/right")
column.getAfter("left/right")
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://stackblitz.com/edit/vitejs-vite-pn9fmj7c?file=src%2Fmain.tsx
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
Maybe, I'll investigate and start debugging
Terms & Code of Conduct
The text was updated successfully, but these errors were encountered: