stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Add one-handed swipe decisions to mobile Updates triage #769

New Issue
Closed
opened 2026-08-13 20:21:05 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 20:21:05 +00:00
Owner
Copy Link

User problem

The mobile Updates triage flow now provides a fixed decision bar, but reviewing a long queue still requires repeated precision taps. Operators should be able to classify each loaded update one-handed without losing vertical scrolling, browser edge navigation, accessibility, offline behavior, or Undo.

Scope

  • Swipe right on non-interactive update content: keep unread and advance.
  • Swipe left: use the existing mark-read-and-next path, including offline queueing and Undo.
  • Ignore vertical, edge-origin, multi-pointer, interactive-control, and horizontal-scroller gestures.
  • Keep existing buttons as keyboard/screen-reader fallbacks and respect reduced motion.

Acceptance

  1. A committed right/left horizontal gesture invokes its decision exactly once.
  2. Vertical/sub-threshold/cancelled gestures do not decide.
  3. Gestures beginning on interactive content, horizontal scrollers, or the browser edge are ignored.
  4. UI integration only enables gestures for a loaded item at phone width and shares the existing mutation lock.
  5. Focused tests and full suite pass; shipped browser bundles remain valid.

Evidence / non-duplication

Audited origin/main at 18f5658, all 387 historical issue titles, 378 PRs, releases, and recent commits. No historical swipe/gesture/one-handed triage issue exists. #763 added the fixed thumb-reachable decision bar but not gesture input.

## User problem The mobile Updates triage flow now provides a fixed decision bar, but reviewing a long queue still requires repeated precision taps. Operators should be able to classify each loaded update one-handed without losing vertical scrolling, browser edge navigation, accessibility, offline behavior, or Undo. ## Scope - Swipe right on non-interactive update content: keep unread and advance. - Swipe left: use the existing mark-read-and-next path, including offline queueing and Undo. - Ignore vertical, edge-origin, multi-pointer, interactive-control, and horizontal-scroller gestures. - Keep existing buttons as keyboard/screen-reader fallbacks and respect reduced motion. ## Acceptance 1. A committed right/left horizontal gesture invokes its decision exactly once. 2. Vertical/sub-threshold/cancelled gestures do not decide. 3. Gestures beginning on interactive content, horizontal scrollers, or the browser edge are ignored. 4. UI integration only enables gestures for a loaded item at phone width and shares the existing mutation lock. 5. Focused tests and full suite pass; shipped browser bundles remain valid. ## Evidence / non-duplication Audited origin/main at 18f5658, all 387 historical issue titles, 378 PRs, releases, and recent commits. No historical swipe/gesture/one-handed triage issue exists. #763 added the fixed thumb-reachable decision bar but not gesture input.
timmy self-assigned this 2026-08-13 20:21:05 +00:00
timmy closed this issue 2026-08-13 20:32:45 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#769
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?