major
nice-to-have
defect
major
enhancement
Depending on the drop target, the operation may vary in specificity at the target. In a tree that does not have a user-defined order (where the children of a node are sorted using a comparator), it is not possible to insert an element at a specific position in a node’s list of children. The visual feedback provided to the user must reflect this behavior accordingly. The drop target must be configurable accordingly.
Drop Semantics in the Tree
Possible options: "ordered," "child," and "global."
- With "ordered," insertion can be made at a specific position in the tree. A distinction must be made between inserting next to a node and inserting below a node. #21657 implements only this option, but not fully—within a child list, it cannot distinguish whether the item is being inserted between children or below a child.
- With "child," insertion can only occur below a node. The position within a node’s child list is irrelevant. Therefore, you can simply drag to a node, and the insertion will occur below that target node.
- With "global," only the tree as a whole can be selected as the target. The drop logic automatically determines whether and where the insertion takes place.
Drop Semantics in Tables
Possible options: "ordered," "global." #21657 does not allow dropping into a table.
- With "ordered," you can insert at a specific position between two rows. The drop marker indicates the position during the hover effect.
- With "global," only the table as a whole can be selected as the drop target. There is no drop preview as a hover effect.
Test
- View Technical Demo: Layout Framework#1: Forms: Drag & Drop in tl-demo.