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

Add persistent mobile update workspace navigation #967

New Issue
Closed
opened 2026-08-16 13:33:46 +00:00 by timmy · 0 comments
timmy commented 2026-08-16 13:33:46 +00:00
Owner
Copy Link

Problem

Mobile Updates opens at newest activity and keeps final decisions thumb-reachable, but the conversation, subject context, and reply composer remain one long scrolling workspace. Long paginated threads require repeated swipes between evidence and response controls. Existing persistent navigation covers issue and pull-request sheets only (#961, #965).

Evidence

  • frontend/index.html lays out conversation, context, and reply sequentially in the update sheet.
  • frontend/dashboard.js exposes only one-off Jump to new activity and Reply scrolling controls.
  • Current history contains no update-workspace section navigation issue or commit; related #759/#763 solve positioning and final decisions, not in-sheet navigation.

Acceptance criteria

  • At phone widths, a sticky four-destination rail exposes New activity, Conversation, Subject context, and Reply without overlapping the fixed decision bar.
  • New activity reuses the existing unread marker position; Subject context opens before navigation; Reply preserves the draft and focuses the composer.
  • The visible destination uses aria-current="location" and resets when another update opens.
  • Controls are at least 44px high, safe-area aware, contained at 320px, excluded from swipe decisions, and hidden above 600px.
  • Behavioral controller tests prove navigation, context expansion, reply focus, selection reset, and listener cleanup; focused and full suites pass.
## Problem Mobile Updates opens at newest activity and keeps final decisions thumb-reachable, but the conversation, subject context, and reply composer remain one long scrolling workspace. Long paginated threads require repeated swipes between evidence and response controls. Existing persistent navigation covers issue and pull-request sheets only (#961, #965). ## Evidence - `frontend/index.html` lays out conversation, context, and reply sequentially in the update sheet. - `frontend/dashboard.js` exposes only one-off Jump to new activity and Reply scrolling controls. - Current history contains no update-workspace section navigation issue or commit; related #759/#763 solve positioning and final decisions, not in-sheet navigation. ## Acceptance criteria - At phone widths, a sticky four-destination rail exposes New activity, Conversation, Subject context, and Reply without overlapping the fixed decision bar. - New activity reuses the existing unread marker position; Subject context opens before navigation; Reply preserves the draft and focuses the composer. - The visible destination uses `aria-current="location"` and resets when another update opens. - Controls are at least 44px high, safe-area aware, contained at 320px, excluded from swipe decisions, and hidden above 600px. - Behavioral controller tests prove navigation, context expansion, reply focus, selection reset, and listener cleanup; focused and full suites pass.
timmy self-assigned this 2026-08-16 13:33:46 +00:00
timmy closed this issue 2026-08-16 13:46:41 +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#967
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?