{{ message }}
Repository navigation
[BUG]: Temperature/effort dropdown overlays composer input on mobile web (portrait) — regression #37545
Description
Description
In the OpenCode web UI on mobile in portrait orientation, the temperature/reasoning effort dropdown ("Default"/"High"/"Max") overlays the composer text input area, making it impossible to see or complete what you're typing. Works fine in landscape mode.
Steps to Reproduce
- Open OpenCode web UI on a mobile device (Android/iOS) in portrait mode.
- Start typing a prompt in the composer.
- Tap the temperature/effort selector ("Default").
- The dropdown opens on top of the input area and the send button, obscuring both.
Expected Behavior
The dropdown should push the composer up or open upward so the input remains visible and usable.
Screenshots
Attached — the "Default"/"High"/"Max" menu covers the text being typed and the send area.
Environment
- Mobile portrait mode (landscape is unaffected)
- Tested on Chrome Android / Edge Android
- opencode web v1.18.3
Additional Context
This is a regression — likely introduced by the v2 Desktop migration (v1.18.0). The previous keyboard-coverage bug (#15842) was fixed via viewport interactive-widget changes, but the dropdown overlay is a separate issue introduced in the v2 UI layout.
Metadata
Metadata
Assignees
Labels
No labels
Activity
Capicua25x commentedon Aug 22, 2026
Friendly bump — this has been open a month (since 07-17) with no triage, and it still affects the mobile web UI, which is the primary way many users reach opencode from a phone.
To be concrete about why it matters beyond cosmetics: in portrait the dropdown covers both the active text being typed and the send control, so a user literally cannot see their own prompt or submit — it's a usability blocker on mobile, not a nit. It's also a regression from the v2 layout (landscape and pre-v2 desktop were both fine).
Happy to help close it however is most useful: I can attach a fresh repro against the current release, test a candidate fix on real Android Chrome/Edge, or write up the specific CSS/interactive-widget change that would restore the pre-regression behavior. Just let me know what's most useful — otherwise, if there's a more appropriate repo/milestone for web-UI issues, point me there and I'll re-file.