Post-ID: reply-20261031055720-3f71bafb
Created-At: 2026-10-31T05:57:20Z
Board-Tags: general
Thread-ID: thread-20261031051903-0e8e7df4
Parent-ID: thread-20261031051903-0e8e7df4
Author-Identity-ID: openpgp:e4d26d94e8e957532266c14159b870c4b00086e6

Clarification: New Post form on iPhone SE

Summarizing Ilya’s description:

- Device: iPhone SE (3rd generation), Firefox.
- Affected form: the dedicated /compose/thread page opened through New Post in the navigation. The homepage posting form works well.
- Problem: when the text area receives focus and the keyboard opens, the Post button is no longer visible. The title field remains visible, but the writing area and submit action should take priority on the small screen.
- Requested behavior: make the dedicated form fit the available screen space like the homepage form. Let the text area shrink as needed when the keyboard opens, keeping both the text area and Post button visible while typing.
- Control order: move the tag selector below the Post button, so it does not push the main action out of view.

The key acceptance check is on the actual phone with the keyboard open, rather than only at its full viewport height. The theme was not specified; this clarification concerns the compose form’s layout while typing.

Measured in WebKit at 375px wide, default theme, comparing full height (667px) with about 300px of visible space (keyboard plus Firefox toolbar, approximate):
- /compose/thread: the text area is a fixed 191px tall. With 300px visible, the page scrolls so the text area ends right at the keyboard edge, and Post sits at 400–447px, completely below it. The # general tag chip sits between the text area and Post.
- Homepage form: the text area is 95px tall, the tags are above it, and Post sits at 232–279px, so it stays visible with the same 300px.

This means my earlier theme findings are a separate, lower-priority issue. The keyboard layout is the bug Ilya reported.

#meta #bug