Fixed Copy:true elements are not sortable after drop#337
Fixed Copy:true elements are not sortable after drop#337lukasoppermann merged 1 commit intolukasoppermann:masterfrom mfriesen:copyfix
Conversation
|
Hey @mfriesen, thank you very much. It is a nice idea! It might be due to using One way of solving this could be similar to #338 and adding a |
|
@lukasoppermann Have a look now. I think I got everything working. I added logic to find the correct sortable from the e.target |
|
Nice, will have a look as soon as possible, thank you. |
| }, options.debounce) | ||
| // Handle dragover and dragenter events on draggable items | ||
| var onDragOverEnter = function (e) { | ||
| var element = e.target |
There was a problem hiding this comment.
This element is a <td> in tables, which is why it does not work for tables. We need to this because it means tables currently don't work.
Maybe you can just use .closest(options.item) because closest should return the item, if it matches the selector and go up the dom tree if it does not.
There was a problem hiding this comment.
This is still a problem, as it still returns <td>
|
Hey, so I merged #343 which sadly makes this PR "break". However the adjustments are minor:
Sorry for the inconvenience, I just needed to merge this so #259 can be started. Looking forward to your update. Maybe you can just use |
|
@lukasoppermann I've fixed the branch |
|
Hey, sorry, but I think it is not fixed yet. The table still does not work, as |
|
@lukasoppermann I think it's all fixed now. |
|
Neat, thank you. I will give the master branch a bit more manual testing and than we can build another release with the copy feature included. 👍 |
This Pull Request fixes the #311 issue.
I changed the drag/drop events to work at the SortableElement level, so when elements are added to a SortableElement, the automatically inherit all events.