Potential change to address Issue#456

[Lemonsavery]

#456

[coveralls]

Coverage remained the same at 76.864% when pulling 43f1d7b on Lemonsavery:patch-1 into 0b73cd1 on lukasoppermann:master.

[Lemonsavery]

I encountered the same issue as described in #456, and this was part of my fix for it. My issue would occur while using Chrome, but not while using Edge.

[lukasoppermann]

Hey @Lemonsavery
thank you very much for the PR. I will have to look into it to to make sure it has not repercussions and hope to be able to merge it very soon. Great. 👍

[lukasoppermann]

Hey @Lemonsavery can you please explain the issue it is solving again? I have the feeling the issue mentioned in the ticket persists, but this may be due to me not really getting how to reproduce it. 😁

[Lemonsavery]

@lukasoppermann Here are two gifs of rows being dragged and dropped quickly/normal. Drag events are printed to Chrome DevTools console. When dragged and dropped too quickly, the 'drop' event can occur before the placeholder row is in place. insertNode() then tries to use the placeholder as referenceNode, but referenceNode.nextElementSibling is null, so the dragged row vanishes. Then, later, the placeholder row is created.