Skip to content

Question panel leaves only a small scrolling area on iPhone Duo #24290

Closed

Description

@obinnanwachukwu1

What happened

One question with three short options opens in a panel whose answer content has very little vertical space. The user has to scroll through a narrow strip even with the keyboard closed.

Diagnosis

ThreadDetailScreen reserves lastKnownKeyboardHeight or an estimated 336 points even while the keyboard is closed. derivePendingUserInputMaxHeight subtracts this reserve from the window height. PendingUserInputCard fixes the heading and action controls outside a flex-shrinking ScrollView. On a short display, these fixed elements can consume most of the available card height. This is a plausible explanation for the recording, not a measured device layout trace.

Suggested direction: compute room from the actual usable pane and keyboard frame, with keyboard animation handled on the UI thread so a larger closed-keyboard panel does not flash across the header. Guarantee useful answer space; on short layouts, scroll the panel body and secondary controls together while preserving an accessible submit action. A taller fixed maximum alone would not correct the keyboard reserve.

Source investigation uses upstream main at 6c21798, fetched 2026-10-23. The exact source commit of the App Store binary is unverified. The recording proves the visible symptom; source explanations below are hypotheses, not a device-verified root cause.

Source references:

activeUserInputRequestId !== null && collapsedUserInputRequestId === activeUserInputRequestId;


className="overflow-hidden gap-2.5 rounded-[20px] border border-border bg-card-alt p-4"

Steps to reproduce

  1. Open a Codex thread in the iPhone Duo App Store app.
  2. Ask the agent to ask one question with the structured question tool.
  3. Use this prompt: "What’s something you’d like to learn just for fun?" with options "Play an instrument", "Speak a new language", and "Cook a new cuisine".
  4. Leave the keyboard closed and scroll the expanded answer panel.
    Expected: enough usable space to read and select answers. Observed: only a narrow part of the content is visible at once.

Version

2.1.0, stable iOS App Store release, user-reported.

Environment

T3 Code iOS app 2.1.0, stable App Store release, as reported by the user. iPhone Duo. Exact iOS version and app build number not recorded. Codex harness, gpt-6.1-sol. Other devices were not tested.

Evidence and related issues

The first 8 seconds of the approved 14-second recording show scrolling inside the constrained panel. The original screenshot also shows the first option clipped below the question.

Related: #5009 was closed after a bounded ScrollView was added. This report concerns an existing ScrollView being starved of space, with only one short question, rather than a completely non-scrollable multi-question card.

Fix applied or workaround

No app/source changes applied. No device-specific workaround verified.

Filed by

GPT-6.1 Sol through the Codex harness in T3 Code. Source investigation only; no local app patch applied.

Uploaded evidence

Watch the approved 14-second recording

Browser tab pill overlapping the expanded question panel

The cut retains source ranges 0–8 seconds and 16.5–22.5 seconds. The screenshot is from source 18.5 seconds. Media is hosted on the reporter's fork as GitHub release assets.

Companion report from the same recording: #24291.

Activity

  1. juliusmarminge commented on Oct 27, 2026

    @juliusmarminge
    Member

    Fixed on main by d0e621e (https://git.cafe/pingdotgg/t3code/pulls/24363), merged 2026-10-24. That merge is what closed this issue.

    The question card no longer reserves an estimated 336 pt keyboard height while the keyboard is closed. Its max height now follows the live keyboard frame on the UI thread, so with the keyboard closed the card gets the full pane below the header. On the Duo's unfolded layout, when the composer does not own the keyboard, no keyboard space is reserved at all.

    Checked on main at 32bf48f with the layout function from main. Assumed: 100 pt header and 90 pt composer. With the keyboard closed, the card's max height:

    • 620 pt window: 160 pt before, 418 pt now
    • 700 pt window: 162 pt before, 498 pt now
    • 844 pt window: 306 pt before, 560 pt now (560 pt is the cap)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions