-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[bug] Can't cancel swap once an item has been hovered over #1866
Comments
+1 |
I agree that your description is how it intuitively should work. Accepting PR's! |
hi everyone! @yjukaku did you find any workaround ? |
I did not. |
I've made a fix here: JoakimFFCG@90c4f89#diff-b4ffb7cc6e458fc5b1fca6d2ee32068db651d86a4b1bf5df9e411bcb10d2be40 Here is a demo: https://jsbin.com/zefoloboyi/edit?html,js,output There have been a lot of changes in the master branch since 1.10.2 and when I compiled the source in the master branch myself, the swap plugin appeared to be broken (as in, the swap option didn't alter the behaviour at all; items were sorted normally). Problem details |
Any news on that? |
any updates? |
Got the same problem here, any updates on the great fix of @JoakimFFCG ? :) |
Swap plugin now cancels the swap when dragging an element over invalid drop targets.
Is this out of progress? |
@wChenonly |
Any updates about this issue? |
Are there any more updates for this? The issue still persists in version 1.15.2. |
Describe the bug
When using the Swap plugin, it's impossible to cancel a swap once the swap threshold has been met for an item. You can't drag the item back to its original place to prevent a swap. This happens with or without the
revertOnSpill: true
option.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Dragging Item 1 back to its original place, or off of the list, should deactivate the swap.
Information
Sortable.version == 1.10.2
I didn't include a code sandbox since it's visible with Sortable.js's own Github site.
Thank you so much for your work on this library!
The text was updated successfully, but these errors were encountered: