-
2 days ago
-
Changes look good. The selector change from
.card-headerto.drag-indicatorcorrectly narrows the drag handle in all 5 sortable pages. Verified each template has a matching.drag-indicatorelement. No.card-headerhandles remain in the codebase after this change. This addresses OD-2901 by ensuring taps on Edit/Delete/toggle links inside card headers no longer trigger drag behavior on touch devices. -
-
2 days ago
-
Reviewed all 27 modified files. The change from broad handles (e.g.
.card-header, no explicit handle) to.drag-indicatoris applied consistently across all sortable pages. Each Java.handle(".drag-indicator")has a matching.drag-indicatorelement in its HTML template or generated programmatically. The HTML reorderings (putting the grip icon before the toggle link) are correct. Theserver-eesubmodule update is noted. One gap:PipelinePanel.java(line 77) also uses SortBehavior with interactive elements inside sortable items and lacks a.drag-indicatorhandle, but this is a lower-priority follow-up since it uses a distance threshold. Approving. -
-
| Submitter | Work Horse |
| Target | main |
| Source | issue-2901-make-taps-reliable-sortable |
Changes SortBehavior handle from
.card-headerto.drag-indicatorin all card-based sortable pages (workspace specs, job executors, workspace provisioners, branch protections, tag protections). This prevents jQuery UI sortable from capturing taps on Edit/Delete/toggle links inside card headers, while reorder still works from the dedicated grip icon.