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

Preserve mobile My Work section history across Back and reload #1006

New Issue
Closed
opened 2026-08-17 06:50:18 +00:00 by timmy · 0 comments
timmy commented 2026-08-17 06:50:18 +00:00
Owner
Copy Link

Problem

Mobile My Work detail sheets have section rails, but section changes are not URL-addressable. Hardware/browser Back exits the entire sheet, and reload/PWA restoration loses the active section. Existing item-level routing (#205/#206) and section rails (#961/#962, #965/#966, #967/#968, #969/#970) do not preserve section state.

User flow

For issue, pull request, update, and requested-review details: explicit section taps create Back-safe history; passive scroll replaces the current section entry; valid section URLs restore the exact section without reopening/refetching the item or forcing composer focus. Invalid or kind-incompatible sections normalize safely.

Acceptance criteria

  • Valid sections round-trip through My Work routes for each detail kind.
  • A rail tap pushes one history entry; passive visibility updates replace instead of push.
  • Back moves to the prior section before leaving the detail sheet.
  • Reload restores the section and aria-current without opening the keyboard.
  • Changing items resets to that item’s default section.
  • Existing drafts, reduced-motion, desktop, item routes, and queue routes remain unchanged.
  • Focused behavioral tests and the full suite pass.

Non-duplication evidence

All 505 historical issue titles and recent origin/main commits were checked. Related shipped work covers item-level routes or scroll/focus rails only; no issue or commit covers section URL/history/restoration.

## Problem Mobile My Work detail sheets have section rails, but section changes are not URL-addressable. Hardware/browser Back exits the entire sheet, and reload/PWA restoration loses the active section. Existing item-level routing (#205/#206) and section rails (#961/#962, #965/#966, #967/#968, #969/#970) do not preserve section state. ## User flow For issue, pull request, update, and requested-review details: explicit section taps create Back-safe history; passive scroll replaces the current section entry; valid section URLs restore the exact section without reopening/refetching the item or forcing composer focus. Invalid or kind-incompatible sections normalize safely. ## Acceptance criteria - Valid sections round-trip through My Work routes for each detail kind. - A rail tap pushes one history entry; passive visibility updates replace instead of push. - Back moves to the prior section before leaving the detail sheet. - Reload restores the section and aria-current without opening the keyboard. - Changing items resets to that item’s default section. - Existing drafts, reduced-motion, desktop, item routes, and queue routes remain unchanged. - Focused behavioral tests and the full suite pass. ## Non-duplication evidence All 505 historical issue titles and recent origin/main commits were checked. Related shipped work covers item-level routes or scroll/focus rails only; no issue or commit covers section URL/history/restoration.
timmy self-assigned this 2026-08-17 06:50:18 +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#1006
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?