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

Consolidate mobile My Work actions into the thumb dock #651

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

Problem

On phone viewports, My Work presents a five-button header action strip directly above the persistent five-item thumb dock. Find and New are duplicated, while Plan/Start duplicates the adaptive Work dock action. At 320px, the forced single-row header actions fall below a reliable 44px target width and consume vertical space before the active queue. Recaps is the only unique destination in the header strip.

Slice

Make the thumb dock the single mobile command surface: hide the redundant My Work header action strip at phone widths and add Recaps to the mobile Queues sheet, routing it to the existing recap-history flow. Keep desktop actions unchanged.

Acceptance

  • At phone widths the My Work header action strip is hidden and the dock remains the sole Work/Find/New/Search/Queues surface.
  • The Queues sheet exposes Recaps and selecting it closes the sheet and opens existing recap history without changing Today state.
  • Queue focus restoration and existing queue launches remain intact.
  • Above the mobile breakpoint, existing header actions remain visible and unchanged.
  • Automated behavior/markup/responsive tests cover the flow.

Evidence / non-duplication

Current main renders both surfaces; frontend/index.html contains duplicate actions and frontend/dashboard.css forces them into one mobile row. Historical work added the dock, adaptive Work, queue switching/launching and Updates, but no open/closed issue removes the duplicate strip or moves Recaps into the queue model. No open PR exists.

Implementation files: frontend/index.html, frontend/dashboard.css, frontend/dashboard.js, frontend/mobile-task-dock.js, tests/test_mobile_task_dock.py.

## Problem On phone viewports, My Work presents a five-button header action strip directly above the persistent five-item thumb dock. Find and New are duplicated, while Plan/Start duplicates the adaptive Work dock action. At 320px, the forced single-row header actions fall below a reliable 44px target width and consume vertical space before the active queue. Recaps is the only unique destination in the header strip. ## Slice Make the thumb dock the single mobile command surface: hide the redundant My Work header action strip at phone widths and add Recaps to the mobile Queues sheet, routing it to the existing recap-history flow. Keep desktop actions unchanged. ## Acceptance - At phone widths the My Work header action strip is hidden and the dock remains the sole Work/Find/New/Search/Queues surface. - The Queues sheet exposes Recaps and selecting it closes the sheet and opens existing recap history without changing Today state. - Queue focus restoration and existing queue launches remain intact. - Above the mobile breakpoint, existing header actions remain visible and unchanged. - Automated behavior/markup/responsive tests cover the flow. ## Evidence / non-duplication Current main renders both surfaces; frontend/index.html contains duplicate actions and frontend/dashboard.css forces them into one mobile row. Historical work added the dock, adaptive Work, queue switching/launching and Updates, but no open/closed issue removes the duplicate strip or moves Recaps into the queue model. No open PR exists. Implementation files: frontend/index.html, frontend/dashboard.css, frontend/dashboard.js, frontend/mobile-task-dock.js, tests/test_mobile_task_dock.py.
timmy self-assigned this 2026-08-12 12:49:55 +00:00
timmy closed this issue 2026-08-12 13:04:39 +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#651
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?