WRP-14782: Fixed containers being copied instead of moved in agate/DropManager #742
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enact-DCO-1.0-Signed-off-by: Daniel Stoian daniel.stoian@lgepartner.com
Checklist
Issue Resolved / Feature Added
When performing many item moves in a short time, sometimes one of the items got duplicated, and the other one dissapeared, instead of switching the items between them.
Resolution
While debugging the qa-drag-and-drop, I discovered that the dragOrigin node was the parent element of the dropManager and not one of the slot items. The solutin was to check , in touchEnd event handler, if the dragOrigin has a data-slot attribute.
Additional Considerations
Links
WRP-14782
Comments