You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-09-04] Reduce wasted white space when editing expense/report fields (let the input grow) #96905
When editing a field on an expense or report in NewDot — for example the report title — there's a lot of wasted vertical space around the input. The edit view feels sparse and the text box doesn't make good use of the available space.
This is distinct from #95564, which covers reducing scrolling on the main expense creation form. This issue is specifically about the field-editing views (e.g. editing the report title).
Proposed change
Let the input/text box grow to make better use of the space and reduce the wasted white space in the field-editing view.
Context
Raised via customer feedback (customer finds a lot of wasted space when editing things like the report title in ND). In the discussion, the team agreed we should let the text box grow, and that this needs its own issue separate from the expense-form scrolling work.
The single-field edit pages (report title/text field, room name, expense merchant, etc.) wrap the form in styles.flexGrow1 so the form region expands to fill the whole screen, but the input inside it is a fixed single-line TextInput sitting in a non-growing <View style={styles.mb4}> wrapper. The input never grows, so all of the flexGrow1 space below it is left empty until the Save button — that's the wasted white space.
What changes do you think we should make in order to solve the problem?
Enable the existing grow mode on the field-edit inputs, mirroring the description pages that already work this way:
On the input in EditReportFieldText.tsx, pass autoGrowHeight with a maxAutoGrowHeight, as done in RoomDescriptionPage/IOURequestStepDescription.
If the goal is for the input to fill the entire remaining space (not just up to the default 115px cap in variables.ts:364), also make the wrapping <View style={styles.mb4}> and the input flexible (e.g. flex1) so it consumes the flexGrow1 region instead of stopping at the fixed cap.
Investigation details & scope notes
FormProvider gets styles.flexGrow1 at EditReportFieldText.tsx:69, expanding to full height; the input at line 78-89 is a plain single-line TextInput (no multiline/autoGrowHeight), so it stays ~52px tall (variables.componentSizeLarge).
In BaseTextInput, autoGrowHeight flips the input to multiline and applies the growing container style; height clamps between a min and maxAutoGrowHeight, then scrolls above the max.
Open design question for @Expensify/design: a report title is conceptually one line — should it truly grow to fill the screen, or just become a taller/multiline box up to a sensible cap? This decision drives whether we use option 1 (capped grow) or option 2 (fill remaining space). The wasted-space fix is the same mechanism either way; the cap is the design call.
This is a frontend-only change in Expensify/App; no other repos involved.
What alternative solutions did you explore? (Optional)
Instead of growing the input, the layout could be top-anchored (remove flexGrow1) so the input sits naturally with content below it — but that leaves the space empty rather than using it, which is the opposite of the request. Letting the input grow (reusing the existing autoGrowHeight support) is the lower-risk, already-proven approach.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/96905) to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
One thing to lock down before implementation: the proposal flagged an open design decision that changes what gets built:
Option 1 — capped grow: enable autoGrowHeight + maxAutoGrowHeight (input grows up to a sensible cap, ~115px default). Matches how the description pages already behave.
Option 2 — fill remaining space: additionally make the wrapper and input flex1 so the box consumes the full flexGrow1 region down to the Save button.
A report title is conceptually one line, so growing it to fill the entire screen may look odd — this is a call for @Expensify/design / Julesssss. The wasted-space mechanism is identical either way; only the cap differs.
Once someone confirms which option, reply with @MelvinBot implement [this](https://github.com/Expensify/App/issues/96905#issuecomment-5110986586) and I'll open a draft PR.
Option 1 — capped grow: enable autoGrowHeight + maxAutoGrowHeight (input grows up to a sensible cap, ~115px default). Matches how the description pages already behave.
Option 2 — fill remaining space: additionally make the wrapper and input flex1 so the box consumes the full flexGrow1 region down to the Save button.
Option 1 is the production behavior on all multiline input pages so I prefer this.
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: improvement
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
trjExpensify commentedon Jul 28, 2026
CC: @Expensify/design for vis.
melvin-bot commentedon Jul 28, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mkhutornyi (
External)melvin-bot commentedon Jul 28, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022082250609695140836
MelvinBot commentedon Jul 28, 2026
Proposal
What is the root cause of that problem?
The single-field edit pages (report title/text field, room name, expense merchant, etc.) wrap the form in
styles.flexGrow1so the form region expands to fill the whole screen, but the input inside it is a fixed single-lineTextInputsitting in a non-growing<View style={styles.mb4}>wrapper. The input never grows, so all of theflexGrow1space below it is left empty until the Save button — that's the wasted white space.For the report title specifically, the responsible layout is
EditReportFieldText.tsx:68-89(rendered fromDynamicEditReportFieldPage.tsx:194-203). The same fixed-input pattern lives inRoomNamePage.tsxandIOURequestStepMerchant.tsx.The good news:
TextInputalready supports a grow-to-fill mode (autoGrowHeight+maxAutoGrowHeight) — seeBaseTextInput/types.ts:71-90. It's simply not enabled on these pages. Sibling pages already use it:RoomDescriptionPage.tsx:128-129andIOURequestStepDescription.tsx:219-220.What changes do you think we should make in order to solve the problem?
Enable the existing grow mode on the field-edit inputs, mirroring the description pages that already work this way:
EditReportFieldText.tsx, passautoGrowHeightwith amaxAutoGrowHeight, as done inRoomDescriptionPage/IOURequestStepDescription.variables.ts:364), also make the wrapping<View style={styles.mb4}>and the input flexible (e.g.flex1) so it consumes theflexGrow1region instead of stopping at the fixed cap.Investigation details & scope notes
FormProvidergetsstyles.flexGrow1atEditReportFieldText.tsx:69, expanding to full height; the input at line 78-89 is a plain single-lineTextInput(nomultiline/autoGrowHeight), so it stays ~52px tall (variables.componentSizeLarge).BaseTextInput,autoGrowHeightflips the input to multiline and applies the growing container style; height clamps between a min andmaxAutoGrowHeight, then scrolls above the max.Expensify/App; no other repos involved.What alternative solutions did you explore? (Optional)
Instead of growing the input, the layout could be top-anchored (remove
flexGrow1) so the input sits naturally with content below it — but that leaves the space empty rather than using it, which is the opposite of the request. Letting the input grow (reusing the existingautoGrowHeightsupport) is the lower-risk, already-proven approach.Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/96905)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
mkhutornyi commentedon Jul 29, 2026
@MelvinBot's proposal looks good to me.
🎀 👀 🎀 C+ reviewed
melvin-bot commentedon Jul 29, 2026
Triggered auto assignment to @Julesssss, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
MelvinBot commentedon Jul 29, 2026
Thanks for the review,
mkhutornyi! 🎀One thing to lock down before implementation: the proposal flagged an open design decision that changes what gets built:
autoGrowHeight+maxAutoGrowHeight(input grows up to a sensible cap, ~115px default). Matches how the description pages already behave.flex1so the box consumes the fullflexGrow1region down to the Save button.A report title is conceptually one line, so growing it to fill the entire screen may look odd — this is a call for
@Expensify/design/Julesssss. The wasted-space mechanism is identical either way; only the cap differs.Once someone confirms which option, reply with
@MelvinBot implement [this](https://github.com/Expensify/App/issues/96905#issuecomment-5110986586)and I'll open a draft PR.mkhutornyi commentedon Jul 29, 2026
autoGrowHeight+maxAutoGrowHeight(input grows up to a sensible cap, ~115px default). Matches how the description pages already behave.flex1so the box consumes the fullflexGrow1region down to the Save button.Option 1 is the production behavior on all multiline input pages so I prefer this.
@Expensify/design which option do you prefer?
24 remaining items
mkhutornyi commentedon Sep 2, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: improvement
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/679771
Regression Test Proposal
Test:
Precondition:
Case 1. The box grows with the text
Case 2. Enter saves the title
Case 3. Shift+Enter also saves (desktop web only)
Case 4. Pasting text that spans several lines
5. Editing a long title that already exists
Do we agree 👍 or 👎
The linked 2 deploy blockers are not regressions. Reasoning:
Zapier Logs
Run ID: 00040eee-affe-ac48-df50-763550629fa4melvin-bot commentedon Sep 3, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Sep 3, 2026
Payment Summary
Resolving PRs:
Let single-field edit input grow to reduce wasted white space #97489
Reviewer: @mkhutornyi owed $250 via NewDot
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Sep 8, 2026
Payment Summary
Contributor+: @mkhutornyi due $250 via NewDot
trjExpensify commentedon Sep 17, 2026
approved $250 for @mkhutornyi