Skip to content
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

dragging the component from the left side. its not going back to original position #507

Open
prashanthvdckap opened this issue Jun 12, 2024 · 5 comments

Comments

@prashanthvdckap
Copy link
Contributor

prashanthvdckap commented Jun 12, 2024

When dragging the component from the left side, if it's not dropped into the dropzone, it doesn't return to its original location. Instead, it moves to a different location. I've noticed that your recent commit seems to be causing this issue. However, it worked fine in version 0.14. i have also attached how iam used my component list

image

image

@chrisvxd
Copy link
Member

@prashanthvdckap I'm unable to reproduce this in the demo app. Can you share a codepen that reproduces the issue?

@prashanthvdckap
Copy link
Contributor Author

Hi @chrisvxd
i have attached codesandbox please check their

Sandbox link

@chrisvxd
Copy link
Member

Closing this as I believe it is a user-land issue (as discussed via Discord). Please comment if it's still an issue.

@chrisvxd chrisvxd closed this as not planned Won't fix, can't repro, duplicate, stale Jul 11, 2024
@IMythx
Copy link

IMythx commented Jul 11, 2024

Closing this as I believe it is a user-land issue (as discussed via Discord). Please comment if it's still an issue.

i got the same issue too and idk how to fix it

@chrisvxd
Copy link
Member

@IMythx The issue here in @prashanthvdckap's example is that the component list is flowing horizontally, with wrapping.

However, the <Drawer> component cannot handle wrapping. By default it expects a vertical list of components. If you want to use a horizontal list, you must use direction="horizontal" (I notice a documentation gap here).

I will actually keep this open as a bug, which should be resolved as part of #123 since the underlying dnd behaviour is being reworked.

@chrisvxd chrisvxd reopened this Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants