You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bug show case - http://codepen.io/tedbeer/pen/MwXEZg
It happens when a drop zone inside another drop zone is bigger than the parent.
DnD manager looks for a drop target and selectы the smallest. It does not take into account that a child node can be bigger than a parent node.
I propose changing the algorithm a bit:
find all targets intersecting with the drag source
from related targets (parent-child-descendant) leave the deepest (descendants) only
among remaining targets choose the target with the biggest intersection
The bug show case - http://codepen.io/tedbeer/pen/MwXEZg
It happens when a drop zone inside another drop zone is bigger than the parent.
DnD manager looks for a drop target and selectы the smallest. It does not take into account that a child node can be bigger than a parent node.
I propose changing the algorithm a bit:
The pen using patched amplesdk - http://codepen.io/tedbeer/pen/KpeBBz
Here the patch implementing the algorithm and solving the problem:
The text was updated successfully, but these errors were encountered: