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

Continue through mobile Search results while planning work #801

New Issue
Closed
opened 2026-08-14 04:50:44 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 04:50:44 +00:00
Owner
Copy Link

User problem

Mobile Search previews force operators back to the result list after every inspection or successful Add to Today / Defer action. Reviewing a result set therefore requires repeated taps and visual reacquisition.

Slice

Add Previous/Next navigation and an accessible position indicator to the Search preview. Keep the current Search session and scroll, replace preview history in place, load the next result page at the loaded boundary, and advance after confirmed Add to Today or Defer outcomes.

Acceptance criteria

  • At 320px and 390px widths, Previous/Next are 44px touch targets with no horizontal overflow and expose an accessible N of M position.
  • Adjacent navigation preserves query, scope, loaded results, and list scroll; browser Back returns directly to Search rather than traversing preview items.
  • Next at the loaded boundary fetches the next page once; true end announces Search pass complete.
  • Successful Add to Today / Defer advances; failures remain on the current result.
  • Rapid navigation cannot render stale preview responses.
  • Focused behavioral tests and the full suite pass.

No historical issue or recent commit covers sequential Search preview navigation; #781-#799 cover resumability, pagination, opening, sharing, filters, repository scope, Today, and Later actions only.

## User problem Mobile Search previews force operators back to the result list after every inspection or successful Add to Today / Defer action. Reviewing a result set therefore requires repeated taps and visual reacquisition. ## Slice Add Previous/Next navigation and an accessible position indicator to the Search preview. Keep the current Search session and scroll, replace preview history in place, load the next result page at the loaded boundary, and advance after confirmed Add to Today or Defer outcomes. ## Acceptance criteria - At 320px and 390px widths, Previous/Next are 44px touch targets with no horizontal overflow and expose an accessible `N of M` position. - Adjacent navigation preserves query, scope, loaded results, and list scroll; browser Back returns directly to Search rather than traversing preview items. - Next at the loaded boundary fetches the next page once; true end announces `Search pass complete`. - Successful Add to Today / Defer advances; failures remain on the current result. - Rapid navigation cannot render stale preview responses. - Focused behavioral tests and the full suite pass. No historical issue or recent commit covers sequential Search preview navigation; #781-#799 cover resumability, pagination, opening, sharing, filters, repository scope, Today, and Later actions only.
timmy self-assigned this 2026-08-14 04:50:44 +00:00
timmy closed this issue 2026-08-14 05:13:10 +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#801
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?