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

Keep mobile issue capture visible above the keyboard #489

New Issue
Closed
opened 2026-08-10 14:19:15 +00:00 by timmy · 0 comments
timmy commented 2026-08-10 14:19:15 +00:00
Owner
Copy Link

Evidence

The mobile New issue sheet immediately focuses repository search or title, but it is omitted from the shared visualViewport controller and keyboard-active CSS that already protect conversation composers. On phone keyboards, repository results, description/validation, and final creation actions can be obscured. Historical issue/commit review found keyboard handling for command search (#317), conversation replies (#323), and the searchable capture repository picker (#487), but no issue covering keyboard-safe issue capture.

User flow

Open New on mobile, search/select a repository, enter title and description, resolve validation, and reach the sticky create actions while the software keyboard is open. Closing the sheet must restore viewport state without losing the draft.

Acceptance tests

  • At mobile width with visualViewport, focus inside the capture form activates viewport geometry on .create-issue-panel.
  • Moving focus among repository search, title, and description reveals the active field without duplicate viewport listeners.
  • Closing the capture sheet clears keyboard geometry/listeners and restores panel scroll.
  • Desktop and browsers without visualViewport retain current behavior.
  • Capture panel CSS uses viewport top/height and remains horizontally contained at 320px.
  • Installed/offline clients receive the updated controller/CSS through a new shell cache revision.
  • Focused and full automated suites pass.
## Evidence The mobile **New issue** sheet immediately focuses repository search or title, but it is omitted from the shared `visualViewport` controller and keyboard-active CSS that already protect conversation composers. On phone keyboards, repository results, description/validation, and final creation actions can be obscured. Historical issue/commit review found keyboard handling for command search (#317), conversation replies (#323), and the searchable capture repository picker (#487), but no issue covering keyboard-safe issue capture. ## User flow Open **New** on mobile, search/select a repository, enter title and description, resolve validation, and reach the sticky create actions while the software keyboard is open. Closing the sheet must restore viewport state without losing the draft. ## Acceptance tests - At mobile width with `visualViewport`, focus inside the capture form activates viewport geometry on `.create-issue-panel`. - Moving focus among repository search, title, and description reveals the active field without duplicate viewport listeners. - Closing the capture sheet clears keyboard geometry/listeners and restores panel scroll. - Desktop and browsers without `visualViewport` retain current behavior. - Capture panel CSS uses viewport top/height and remains horizontally contained at 320px. - Installed/offline clients receive the updated controller/CSS through a new shell cache revision. - Focused and full automated suites pass.
timmy closed this issue 2026-08-10 14:28:58 +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#489
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?