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

Add persistent mobile requested-review workspace navigation #969

New Issue
Closed
opened 2026-08-16 14:22:27 +00:00 by timmy · 0 comments
timmy commented 2026-08-16 14:22:27 +00:00
Owner
Copy Link

Problem

The standalone requested-review sheet is a full-height independently scrolling mobile workspace containing overview/checks, files, feedback, and history, but unlike the issue, pull, and update workspaces it has no persistent section navigation. Reviewers repeatedly scroll long content and lose orientation while moving from context to evidence to decision.

Scope

Add a mobile-only sticky section rail for Overview, Files, Feedback, and History in #review-sheet. Track the visible section, focus the feedback composer when requested, reset on each newly opened review, preserve desktop behavior, reduced-motion preferences, and safe-area/44px touch targets. Cache the new controller in the built offline shell.

Acceptance criteria

  • At 360x800 and 390x844, the rail is visible without horizontal overflow and every target is at least 44px high.
  • Overview, Files, Feedback, and History navigate within the independently scrolling review panel.
  • Active state exposes aria-current="location"; Feedback focuses the summary composer.
  • Opening another review resets navigation to Overview without changing review draft/progress state.
  • Reduced motion uses immediate scrolling; widths above 600px retain existing desktop behavior.
  • Behavioral tests cover controller state/navigation, rendered mobile contract, and offline asset delivery.

Evidence / non-duplication

origin/main has dedicated mobile navigation for issue (#961/#962), pull (#965/#966), and update (#967/#968) workspaces, while #review-sheet remains separate and has no data-review-section or review navigation controller. A scan of all 487 historical issue titles and recent commits found no requested-review workspace navigation issue or implementation.

## Problem The standalone requested-review sheet is a full-height independently scrolling mobile workspace containing overview/checks, files, feedback, and history, but unlike the issue, pull, and update workspaces it has no persistent section navigation. Reviewers repeatedly scroll long content and lose orientation while moving from context to evidence to decision. ## Scope Add a mobile-only sticky section rail for Overview, Files, Feedback, and History in `#review-sheet`. Track the visible section, focus the feedback composer when requested, reset on each newly opened review, preserve desktop behavior, reduced-motion preferences, and safe-area/44px touch targets. Cache the new controller in the built offline shell. ## Acceptance criteria - At 360x800 and 390x844, the rail is visible without horizontal overflow and every target is at least 44px high. - Overview, Files, Feedback, and History navigate within the independently scrolling review panel. - Active state exposes `aria-current="location"`; Feedback focuses the summary composer. - Opening another review resets navigation to Overview without changing review draft/progress state. - Reduced motion uses immediate scrolling; widths above 600px retain existing desktop behavior. - Behavioral tests cover controller state/navigation, rendered mobile contract, and offline asset delivery. ## Evidence / non-duplication `origin/main` has dedicated mobile navigation for issue (#961/#962), pull (#965/#966), and update (#967/#968) workspaces, while `#review-sheet` remains separate and has no `data-review-section` or review navigation controller. A scan of all 487 historical issue titles and recent commits found no requested-review workspace navigation issue or implementation.
timmy self-assigned this 2026-08-16 14:22:27 +00:00
timmy closed this issue 2026-08-16 14:32:37 +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#969
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?