Feature: Adjust touch behaviour in Tasks module on mobile

[thesoundhead]

Problem:

When using the Tasks module on mobile, scrolling up or down might accidentally lead to moving tasks around the list/board.

I propose the following to solve this:

Distinguish between long and short touch, where

• long means: I want to grab this task/card and move it around
• short means: I want to scroll

[ulsklyc]

Confirmed, and the fix is smaller than the report suggests: the behaviour you are asking for already exists in the codebase, the Tasks board just does not use it.

public/utils/sortable.js wraps the vendored SortableJS with exactly the distinction you describe:

delay: 120,
delayOnTouchOnly: true,
touchStartThreshold: 5,

Hold for 120 ms to grab, move within 5 px and it stays a scroll - and delayOnTouchOnly keeps the mouse instant, so nothing gets slower on the desktop. Shopping and the category manager go through this wrapper. The Tasks board does not: it uses the browser's native drag and drop (draggable="true" plus dragstart/drop handlers), which has no such threshold and hands the whole gesture to the platform. On a touch screen that is precisely the "I meant to scroll" problem.

So this is not a new feature to design, it is bringing one module onto the path the others already take. It is not a one-line change - the board drags between columns and writes a new status on drop, so it needs SortableJS group handling rather than the single-list reorder that Shopping does - but the touch semantics come for free with the wrapper.

Worth doing, and thank you for the precise description of the two gestures - that is what made it findable.

[ulsklyc]

Shipped in v2.60.0, @thesoundhead.

Dragging a card on the task board now needs a short hold first, so scrolling past a card no longer picks it up and a swipe stays a swipe. With a mouse nothing changed - a card still moves the moment you drag it.

The board had two separate drag implementations; it now uses the same wrapper the rest of the app already used, which is where the hold delay comes from. One thing worth knowing: the archive drop zone is still reachable only by dragging, so it stays out of reach for keyboard and screen reader users. That is tracked separately in #979 rather than left unsaid here.