-
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
Question: Motivation for cloning "originalSource" #242
Comments
@stkao05 what is the exact behaviour that you need? As of the latest pushes to As for cloning behaviour - the reason why we have a
Does that make sense? Please let me know if you need more clarity. @tsov in case you have a better description. |
Thanks for the detail explanation @beefchimi 🙂Glad to see the library is still in active development. Sorry, I am still trying to wrap my head around it. Yes, the original draggable item could be changed in some way during the drag-and-drop process, but I wasn't sure why would that be an issue? |
^ @tsov was there anything you wanted to add here? |
@beefchimi you got it 👍 We should really file an issue about this, this always sounded like a browser bug to me! |
Would there be a side-effect to removing the style attributes which hides the original? The reason I want it is that I want to display the original until I drop the element to its new position. Or is there a more idiomatic way of achieving this? |
Hi @miralize , If removing the |
When an element gets dragged, a clone of the element is created and also the original element will get hidden. Just curious about the motivation for such a behavior 🙂
(For my specific use case... this behavior a bit undesirable, but not really a major issue)
The text was updated successfully, but these errors were encountered: