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

Keep mobile Update decisions within thumb reach #763

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

Problem

The Updates reader places Keep unread in the header and Mark read after the conversation, context, and reply composer. On a phone, the core read-and-advance flow requires scrolling between opposite ends of the sheet.

Acceptance criteria

  • At 320px and 390px, Keep unread, Mark read, and Reply are persistently reachable in a safe-area-aware decision bar while an Update is open.
  • The global mobile task dock is replaced while the Update sheet is open and restored on close.
  • Keep unread and Mark read preserve existing next-item semantics and prevent duplicate pending mutations.
  • Reply focuses the existing draft-preserving composer.
  • Secondary actions remain available through a More disclosure.
  • Controls have accessible continuation labels and 44px touch targets.
  • Focused and full suites pass.
## Problem The Updates reader places Keep unread in the header and Mark read after the conversation, context, and reply composer. On a phone, the core read-and-advance flow requires scrolling between opposite ends of the sheet. ## Acceptance criteria - At 320px and 390px, Keep unread, Mark read, and Reply are persistently reachable in a safe-area-aware decision bar while an Update is open. - The global mobile task dock is replaced while the Update sheet is open and restored on close. - Keep unread and Mark read preserve existing next-item semantics and prevent duplicate pending mutations. - Reply focuses the existing draft-preserving composer. - Secondary actions remain available through a More disclosure. - Controls have accessible continuation labels and 44px touch targets. - Focused and full suites pass.
timmy closed this issue 2026-08-13 18:56:14 +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
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#763
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?