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

Reset mobile work details when advancing to another item #777

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

Problem

Mobile issue, pull-request, and review dialogs reuse scrollable panels but do not reset their scroll offsets when the Today session advances. A newly opened item can therefore begin midway through content inherited from the prior item, hiding identity and context before an operator acts.

Evidence: frontend/dashboard.js openers at openIssueSheet, openPullSheet, and openReviewSheet replace content without positioning their .issue-sheet-panel, .pull-sheet-panel, and .review-sheet-panel. Closed #759 solved this only for Updates, not Today work details. No open issue or recent commit covers this behavior.

Acceptance

  • A different issue, pull request, or review starts at the top of its panel.
  • Reopening the same item preserves its current position.
  • A stale async completion cannot reposition the currently visible item.
  • Behavioral controller tests cover changed identity and same-identity preservation.
  • The complete test suite passes.

User impact

The phone Work → Today → next-item flow always exposes the new item key, title, status, and description before destructive or authorship actions.

## Problem Mobile issue, pull-request, and review dialogs reuse scrollable panels but do not reset their scroll offsets when the Today session advances. A newly opened item can therefore begin midway through content inherited from the prior item, hiding identity and context before an operator acts. Evidence: `frontend/dashboard.js` openers at `openIssueSheet`, `openPullSheet`, and `openReviewSheet` replace content without positioning their `.issue-sheet-panel`, `.pull-sheet-panel`, and `.review-sheet-panel`. Closed #759 solved this only for Updates, not Today work details. No open issue or recent commit covers this behavior. ## Acceptance - A different issue, pull request, or review starts at the top of its panel. - Reopening the same item preserves its current position. - A stale async completion cannot reposition the currently visible item. - Behavioral controller tests cover changed identity and same-identity preservation. - The complete test suite passes. ## User impact The phone Work → Today → next-item flow always exposes the new item key, title, status, and description before destructive or authorship actions.
timmy self-assigned this 2026-08-13 22:20:08 +00:00
timmy closed this issue 2026-08-13 22:30:12 +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#777
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?