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

Add persistent mobile issue detail navigation #961

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

Evidence

The mobile issue sheet is one long scrolling panel: description/checklist, up to 20 conversation messages, the reply composer, planning, handoff, and final actions (frontend/index.html lines 628-815). The panel scrolls as one surface and only the final action block is sticky (frontend/dashboard.css), so Reply and planning can require many swipes. Historical issue/PR title review found no persistent in-sheet navigation; related #205, #209, #215, #323, and #777 address routing, conversation loading, read-first layout, keyboard visibility, and position reset—not section navigation.

User flow

Add a mobile-only sticky action rail with Overview, Conversation, Reply, and Plan & actions. Controls jump to the section, Reply focuses the existing durable composer, Plan opens planning before navigation, and the visible/current destination is exposed with aria-current. Desktop remains unchanged.

Acceptance

  • Four controls are present in the issue sheet with 44px touch targets and no horizontal overflow at 320px.
  • Overview, Conversation, Reply, and Plan & actions navigate to their targets; Reply focuses the composer; Plan expands planning.
  • Reduced-motion preference avoids forced smooth scrolling.
  • The controller tracks the current section accessibly and disconnects cleanly.
  • Focused composer behavior continues through the existing mobile viewport controller.
  • Focused tests and the full suite pass.
## Evidence The mobile issue sheet is one long scrolling panel: description/checklist, up to 20 conversation messages, the reply composer, planning, handoff, and final actions (`frontend/index.html` lines 628-815). The panel scrolls as one surface and only the final action block is sticky (`frontend/dashboard.css`), so Reply and planning can require many swipes. Historical issue/PR title review found no persistent in-sheet navigation; related #205, #209, #215, #323, and #777 address routing, conversation loading, read-first layout, keyboard visibility, and position reset—not section navigation. ## User flow Add a mobile-only sticky action rail with Overview, Conversation, Reply, and Plan & actions. Controls jump to the section, Reply focuses the existing durable composer, Plan opens planning before navigation, and the visible/current destination is exposed with `aria-current`. Desktop remains unchanged. ## Acceptance - Four controls are present in the issue sheet with 44px touch targets and no horizontal overflow at 320px. - Overview, Conversation, Reply, and Plan & actions navigate to their targets; Reply focuses the composer; Plan expands planning. - Reduced-motion preference avoids forced smooth scrolling. - The controller tracks the current section accessibly and disconnects cleanly. - Focused composer behavior continues through the existing mobile viewport controller. - Focused tests and the full suite pass.
timmy self-assigned this 2026-08-16 11:49:33 +00:00
timmy closed this issue 2026-08-16 12:05:56 +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#961
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?