-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataTable: rowReorder not displaying "ghost" row when dragging #6548
Comments
@romanzhukov23 your stackblitz is working fine for me I can reorder the rows using 10.6.4: https://stackblitz.com/edit/vitejs-vite-rrnm2t?file=src%2FApp.tsx |
We're unable to replicate your issue, if you are able to create a reproducer or add details please edit this issue. This issue will be closed if no activities in 20 days. |
Also for me the ROW is never draggable? Only the ICON is draggable. Same as the showcase: https://primereact.org/datatable/#reorder |
I mean, when dragging, only the icon follows the cursor, but not the entire line, as in the default version |
default icon.webm |
Oh I see one sec That makes more sense. |
so can I do anything with this problem?) |
I think it needs to be investigated why its happening with a custom icon... could be a bug. |
Hmmmm, i think i know what is going on here, let me fix it |
Ill be very grateful |
https://stackblitz.com/edit/vitejs-vite-ydodxm?file=src%2FApp.tsx |
iconProps not IconProps |
@romanzhukov23 yep here is a fixed version working fine: https://stackblitz.com/edit/vitejs-vite-fsx4n2?file=src%2FApp.tsx |
Describe the bug
When I replace rowReorderIcon, the row stops being draggable, but only the icon starts to be draggable. What can I do with this to make the string draggable?
Reproducer
https://stackblitz.com/edit/vitejs-vite-ixav5s?file=src%2FApp.tsx
PrimeReact version
10.5.1
React version
18.x
Language
TypeScript
Build / Runtime
Create React App (CRA)
Browser(s)
No response
Steps to reproduce the behavior
Try to drag'n'drop any row
Expected behavior
No response
The text was updated successfully, but these errors were encountered: