[TeodorTaushanov]

Table rows could only be reordered with the mouse, while List already supports reordering movable items with the keyboard. This adds the same keyboard support to the Table.

Pressing Ctrl + Arrow moves a movable row one position; Ctrl + Home/End moves it to the top/bottom. The handler reuses the shared findClosestPositionsByKey utility and fires the existing move-over/move events, mirroring List and TabContainer.

fixes #14135

[sap-ui5-webcomponents-release]

🚀 Deployed on https://pr-14201--ui5-webcomponents-preview.netlify.app

[aborjinik]

... while List already supports reordering movable items with the keyboard. This adds the same keyboard support to the Table.

The handler reuses the shared findClosestPositionsByKey utility and fires the existing move-over/move events, mirroring List and TabContainer.

Aren't these statements an explicit admission that we lack a proper reuse layer?

Ideally, reordering (and many of the already existing d&d implementation) should be implemented in a shared layer so that List, Table, and other applicable controls can reuse the same behavior, including keyboard interactions, drag-and-drop, and move events. Otherwise, every new feature or bug fix must be implemented and maintained separately for each control, leading to duplication and behavioral inconsistencies over time.

[aborjinik]

While looking at the core d&d implementation, I noticed that component d&d logic is needed seemingly because of the dropIndicatorDOM dependency. IMHO you should reconsider this separation. Since a user can only perform one drag operation at a time, the drop indicator could potentially be managed by a single shared instance rather than being owned by individual components.
This would allow you to centralize the drag-and-drop logic in the core implementation, eliminate unnecessary duplication, and decouple the consuming components from the rendering lifecycle of the drop indicator (though components might still need to set the orientation/placement/ownerReference but probably drag events are fine for it).

[dimovpetar]

@aborjinik I have opened #14238 to tackle this.
Otherwise, this PR looks good to me.