[Bug]: Threads in the Working section cannot be dragged into Pinned#28117
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
- Keep Working section on (the default) and have a thread that is running, so it sits in the Working section.
- Expand the Working section.
- Press on the thread and drag it up to the Pinned area.
- Release it there.
Expected behavior
The thread lifts and follows the pointer, like a thread in any other section. The Pinned and Active labels appear, the row shows the Pin badge, and dropping it pins the thread at that spot. Thread menu > Pin already allows this, and a pinned thread stays in Pinned while it works.
Actual behavior
The row stays in place in Working, no drop labels appear, and nothing is pinned on release. The only drag that works is to a composer outside the thread list.
Impact
Minor bug or occasional failure: the thread menu is a workaround.
Version or commit
Reproduced on main at 79f1fadfc6 (after v0.1.6 prep).
Environment
Linux, web client code, Chromium.
Logs or stack traces
None. The block is deliberate code from #19697: planSidebarThreadDrop returns no move for every drop from Working, and isContextDrag treats every Working drag as a drag to the composer.
Screenshots, recordings, or supporting files
During the drag, before any fix:
Row stays in Working during the drag
Related but different: #16137 was about dragging a Working thread into a composer.