pingdotgg / pingdotgg/t3code

[Bug][Mobile] Android composer does not scroll the current line into view while typing a long prompt

Open
#12,690 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Description

On the Android mobile app (Play Store 1.1.0), typing a long multi-line prompt in the chat composer eventually leaves the line I am typing on out of view. The composer stops following the caret, so I am typing blind until I send the message or manually scroll the input.

I could not tell from the app whether the editor stops growing at its max height and then fails to scroll the caret into view, or whether it grows but the caret still ends up outside the visible area (possibly behind the keyboard). Either way, the current line is not scrolled into view while typing.

Expected behavior

  • While typing, the caret/current line is always scrolled into view in the composer, both while the editor is still growing and after it has reached its maximum height.
  • Moving the caret back up to an earlier line should also scroll that line into view.

Notes / possibly related

  • #11987 — iOS composer never grows with the prompt (open). Same family, different platform.
  • #11757 — fix(mobile): grow the composer with the typed prompt (closed, unmerged). Its description says the expanded composer stayed at its min height so "the caret and the end of a long prompt sat off-screen while typing", and that the box is shared between iOS and Android (same Yoga minHeight), but the caret-scroll part of that fix was iOS-only (scrollCaretIntoViewIfNeeded). Android appears to have no equivalent caret-into-view call.
  • #11992 — Android composer and working pill cover the newest transcript lines (open). Different surface (transcript, not the composer's own scroll).
  • #11918 — fix(mobile): keep collapsed Android composer placeholder on one line (open).

Environment

  • Android, T3 Code 1.1.0 (Google Play)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Android composer implementation and compare it with the iOS caret-scroll behavior referenced in #11757, especially the scrollCaretIntoViewIfNeeded path. Reproduce with a long multiline prompt, after the composer reaches its maximum height and after moving the caret upward; done means the current line remains visible while typing and navigating.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.