fixing the input ui at certain endpoints causing the button to overflow. #1574
fixing the input ui at certain endpoints causing the button to overflow. #1574shivamhwp wants to merge 6 commits intopingdotgg:mainfrom
Conversation
- Move send, stop, and plan follow-up controls into a shared component - Add compact pending-question and implementation action variants to avoid overflow
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- Raise the wide-actions compact threshold - Force compact mode when footer content no longer fits - Keep composer actions on one line and add fit tests
- measure footer content width after padding - add overflow-based compactness heuristic - update tests for footer layout behavior
- add browser tests for pending input and plan follow-up footers - mark composer footer/action compact state for layout assertions - remove redundant ComposerPrimaryActions snapshot tests
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
- Update the test description to reflect that minor overflow stays expanded when primary actions can compact - Preserve the intended composer footer layout behavior

origin - https://x.com/KevinVanCott/status/2038274360058753214
What Changed
Previousto an icon in compact mode.Submit answersshortens toSubmitin compact mode.Implementbutton.Why
Resizing the app could leave the composer footer in a state where the right-side action cluster was wider than the available space. The old layout combined several constraints that made overflow inevitable:
Submit answersand the splitImplementbutton had no narrow fallback,This change fixes the root cause instead of just adjusting the breakpoint. The footer actions now have a true compact rendering path, so they still fit when the composer becomes narrow after resize.
UI Changes
Before:
Screen.Recording.2026-03-30.at.3.16.26.PM.mov
After:
Screen.Recording.2026-03-30.at.3.41.59.PM.mov
note: don't mind the lag, it's just my machine having low memory !!
Checklist
Note
Medium Risk
Touches core
ChatViewcomposer layout and action rendering logic, so regressions could impact sending/plan flows across breakpoints, but changes are UI-only with added regression tests.Overview
Fixes composer footer action overflow after resizes by switching from a pure breakpoint heuristic to measured fit:
ChatViewnow tracks footer/primary-action compactness using DOM measurements (footer padding/content widths) and forces compact mode when content would overflow.Extracts the right-side action cluster (send/stop, pending-question navigation, plan follow-up implement/refine) into
ComposerPrimaryActions, adding compact variants (shorter labels, icon-only previous button, compact implement+menu layout). Updates compactness breakpoints/helpers incomposerFooterLayout.ts, adjusts composer sizing/styles (wider max width, overflow-hidden footer), and adds browser + unit tests to ensure actions remain contained after a real container resize.Written by Cursor Bugbot for commit 1ae6d13. This will update automatically on new commits. Configure here.
Note
Fix composer footer button overflow at narrow container widths
max-w-3xltomax-w-[52rem], slightly widening the input area on larger screens.Macroscope summarized 1ae6d13.