[Bug]: Collapsing the question card still leaves the composer at full height, and scrolling never rests it #14231

Activity

1. Vantrongs

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Sep 29, 2026
2. juliusmarminge commented on Sep 29, 2026

   

   juliusmarminge

   on Sep 29, 2026

   Member

   More actions

   Triage

   Confirmed on current main (d2c9281, the commit this report cites). No later commit changes this path.

   The chevron only hides the question body. collapsedQuestionId stays inside ComposerPendingUserInputPanel and toggles that card’s Collapsible. The custom-answer editor and the footer are rendered next to it by ChatComposer, so they stay at full height. That leftover editor is intentional in #6773: a collapsed prompt is still supposed to be answerable.

   Scroll-rest cannot finish the job. showComposerTopDrawer is true for any pendingUserInputs.length > 0, and that sets composerHasExpandedChrome. canScrollCollapseComposer requires expanded chrome to be false, and the effect beside it clears isComposerScrollCollapsed whenever the gate is closed. shouldUseRestingComposerLayout also refuses to rest while hasExpandedChrome is true. The collapsed flag never reaches either check, so with Collapse composer on scroll on, an empty collapsed question still cannot rest. Wheel and keyboard timeline scroll share composerScrollCollapseEligibleRef. This is the desktop path; mobile does not scroll-rest.

   Not a duplicate:

   • feat(web): collapse the question prompt from its header #6773 / [Feature]: Make The Input / Question Prompt Collapsible #4431 added the header chevron. They do not rest the composer.
   • fix(web): preserve multiline composer drafts during timeline scrolling #10444 keeps a multiline draft expanded. A pending custom answer is not prompt (onPromptChange writes the question draft instead), but useComposerMultilinePrompt still measures the editor, so a wrapped answer is already under that guard. An empty answer is not. Leave multiline drafts in discussion [Feature]: Collapsible composer so the thread is readable while a question or approval is pending #6849.
   • [Feature]: Collapsible composer so the thread is readable while a question or approval is pending #6849 is the wider “get the composer out of the way” request (approvals and multiline drafts included). This issue is the pending-question slice already split out there. Approvals use the same expanded-chrome bit and have no chevron; they stay with [Feature]: Collapsible composer so the thread is readable while a question or approval is pending #6849.
   • [Bug]: The composer doesn't rest on scroll when a thread opens above its end, until I scroll to the very end #14232 is a different scroll-rest failure: an unmeasured last row makes timelineOverflows false. Unrelated.

   The focus rule in the report is not how scroll-rest works today. The wheel handler does not look at editor focus. #10437 removed collapse-on-blur; focus still expands a composer that is already resting. Once the chrome gate allows it, a short custom answer would rest on scroll whether or not the caret is in the field. Keeping an in-progress answer open is worth doing in the fix. It should not also start resting multiline drafts.
3. juliusmarminge

   added

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   and removed

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Sep 29, 2026
4. Mnigos

   added a commit that references this issue on Oct 2, 2026

   fix(web): a collapsed question no longer stops the composer from rest…

   ...

   This issue will close once commit c0d1ea4 is merged into the 'main' branch.

   c0d1ea4