Major
Nice to have
Bugfix
Major
Enhancement
Depending on the drop target, the operation in the target can have different specificity. In a tree that does not have a user-defined order (the children of a node are sorted by a comparator), it cannot be inserted at a specific location in the children list of a node. The visual feedback to the user must represent these semantics accordingly. The drop target must be parameterizable accordingly.
Drop semantics in the tree
Possible options: "ordered", "child" and "global".
- With "ordered" a specific position in the tree can be inserted. It must be distinguished whether it is inserted next to a node or below a node. #21657 implements only this option but not completely - it is not possible to distinguish within a child list whether it is inserted between children or below a child.
- With "child" it is only possible to insert below a node. The position within the child list of a node does not matter. Therefore, you can only drag to a node and the insert operation happens below this target node.
- With "global" only the tree as a whole can be selected as a target. The drop logic decides on its own if and where the insert operation takes place.
Drop semantics in tables
Possible options: "ordered", "global". #21657 does not allow any drop in a table.
- With "ordered" it is possible to insert at a specific position between two rows. The drop marker represents the position during the hover effect.
- With "global" only the table as a whole can be selected as drop target. There is no drop preview as hover effect.
Test
- View Technical Demo : Layout-Framework#1 : Forms : Drag & Drop in tl-demo.