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

Keep mobile conversation replies visible above the keyboard #323

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

Problem

On phone-sized screens, focusing the issue, pull-request, or unread-update reply composer leaves the full-height sheet unaware of the software keyboard. The textarea, submit control, and delivery/error status can be obscured. The existing visualViewport controller only covers command search.

Evidence on current main: frontend/index.html defines all three composers; frontend/dashboard.css uses full-height independently scrolling sheets with sticky action regions; frontend/dashboard.js refocuses failed composers without revealing their controls; no historical issue or recent commit covers conversation composers (keyboard work #317 is search-only).

Acceptance criteria

  • On mobile, focusing any of the three conversation textareas sizes and positions its sheet panel from visualViewport.
  • The composer, submit action, and live status are revealed inside the keyboard-reduced viewport after focus, resize, validation failure, or retry.
  • Viewport listeners are attached once, detached on blur/close, and temporary geometry is cleared.
  • Dismissing the keyboard restores prior sheet scroll without changing draft text.
  • Browsers without visualViewport and desktop layouts retain current behavior.
  • The offline shell contains every local runtime asset referenced by the dashboard, including this controller and task-overlay history, with an invariant test preventing drift.
  • Focused tests and the full suite pass.
## Problem On phone-sized screens, focusing the issue, pull-request, or unread-update reply composer leaves the full-height sheet unaware of the software keyboard. The textarea, submit control, and delivery/error status can be obscured. The existing visualViewport controller only covers command search. Evidence on current main: `frontend/index.html` defines all three composers; `frontend/dashboard.css` uses full-height independently scrolling sheets with sticky action regions; `frontend/dashboard.js` refocuses failed composers without revealing their controls; no historical issue or recent commit covers conversation composers (keyboard work #317 is search-only). ## Acceptance criteria - On mobile, focusing any of the three conversation textareas sizes and positions its sheet panel from `visualViewport`. - The composer, submit action, and live status are revealed inside the keyboard-reduced viewport after focus, resize, validation failure, or retry. - Viewport listeners are attached once, detached on blur/close, and temporary geometry is cleared. - Dismissing the keyboard restores prior sheet scroll without changing draft text. - Browsers without `visualViewport` and desktop layouts retain current behavior. - The offline shell contains every local runtime asset referenced by the dashboard, including this controller and task-overlay history, with an invariant test preventing drift. - Focused tests and the full suite pass.
timmy self-assigned this 2026-08-08 17:29:39 +00:00
timmy closed this issue 2026-08-08 17:35:30 +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#323
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?