web: keep empty composer on one line and verify touch sizing

This commit is contained in:
2026-10-20 18:54:45 +01:00
parent 7e9b6771ef
commit 9f5437b5b0
4 changed files with 30 additions and 5 deletions
+9 -3
View File
@@ -65,13 +65,15 @@ restoration. No deployed service, live workflow or device was used.
### Chat audit follow-up (2026-10-20, partial — fresh UI captures pending)
Composer fit follow-up (2026-10-20): CSS-only alignment of attachment, Send and
Composer fit follow-up (2026-10-20): aligned attachment, Send and
Stop controls (44px square; 48px with a coarse pointer), a matching single-line
input, and six complete auto-grown text lines before scrolling. Send remains
available while running; its adjacent Stop slot is reserved even while idle so
state changes do not rewrap a draft. Monochrome CSS SVG masks replace the
platform-dependent button glyph rendering, preserving existing accessible names.
Back/title, chat view/protocol code and keyboard geometry are untouched.
Back/title, protocol and keyboard geometry are untouched. The visible placeholder
is shortened to `Message the agent…` so an empty field stays one aligned line;
the full slash-command hint remains its accessible name.
`node test/composer-fit-browser.mjs ../.ui-composer-fit-after` verifies the real
chat view and input handlers using deterministic fixtures at 390/420/1100px:
empty, single/multiline, running, six/ten-line drafts, attachments and simulated
@@ -79,7 +81,11 @@ keyboard geometry. `--before` serves HEAD's CSS for comparison (run before
committing, or on the parent revision). Captures and `geometry.json` are in
`.ui-composer-fit-before/` and `.ui-composer-fit-after/` in the isolated composer
worktree. This is scratch-browser evidence, not a live-server parity upgrade;
real iOS/Android keyboards and deployed services were not tested.
real iOS/Android keyboards were not tested. Integration additionally captured
28 states under the approved OpenCode temporary `final-composer-fit/` directory,
including browser-emulated coarse pointers at 390/420px: empty input and buttons
are exactly 48px, and adding Stop does not shift the input. Normal-pointer empty
fields and controls are exactly 44px. These are not real-phone keyboard claims.
Codex model follow-up (partial, fixture-tested; fresh UI captures pending):
model controls now include Codex, using the app-server `model/list` catalog and