Repository navigation
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.3.84-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176681/test-cases/41236978
Email or phone of affected tester (no customers): fischer9966+053122@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: MacOS 26.5 / Chrome, Safari, iPhone 17 Pro / 26.5, iPad 9th Gen / 26.5. Pixel 5 / Android 14
App Component: Chat Report View
Action Performed:
- Open Expensify app or go to staging.new.expensify.com
- Login with any account
- Open any chat
- Enter a any text that is over 3 lines to get Expand icon
- Tap "expand" icon to expand composer field
Expected Result:
"Composer" field expands correctly. All elements are visible.
Actual Result:
Composer field is cut off at the bottom when expanded. Mobile apps - bottom part of the composer is hidden by the keyboard. Web - bottom line touches the bottom edge of the screen.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7164845_1779925498667.iOS-expanded-composer-cuts-off.mp4
Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7164845
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022059890385898616348
- Upwork Job ID: 2059890385898616348
- Last Price Increase: 2026-06-11
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
applause-bot commentedon May 28, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/b88a99df65a1ff38c6352448a21982d8a12f45039135ad78cf074198d8ceb77a
https://platform.applause.com/services/links/v1/external/8086fa385186f8154f591acd6903e80c01f3249b53350280de8b7069db16bc64
[-]All - Chat - Composer field is cut off at the bottom when expanded[/-][+]Chat - Composer field is cut off at the bottom when expanded[/+]MelvinBot commentedon May 28, 2026
Proposal
What is the root cause of that problem?
When the composer is expanded to full size,
chatFooterFullComposesetsheight: '100%'on the footer. However, the footer's parent container inReportScreen.tsx:146-147is a flex column withoverflow: 'hidden'that also contains theReportActionsListas a sibling. When the footer requests 100% height, theReportActionsListstill occupies flex space above it — the two siblings compete for the same space. The footer gets pushed down and its bottom is clipped byoverflow: 'hidden'.Additionally,
chatFooterFullComposehaspaddingTop: 20but nopaddingBottom, so the bottom content touches the screen edge on web. On native, the keyboard further reduces available height but the 100% height doesn't account for it, causing the bottom to be hidden behind the keyboard.What changes do you think we should make in order to solve the problem?
When
isComposerFullSizeis true, theReportActionsListsibling inReportScreen.tsx:150should be hidden (e.g.,display: 'none'orflex: 0) so the expanded footer can actually occupy the full parent height without competing for space. Additionally, addpaddingBottomtochatFooterFullComposeto prevent the content from touching the bottom edge.What alternative solutions did you explore? (Optional)
position: 'absolute'on the footer to overlay the actions list — rejected because it would break keyboard avoidance and safe area handling.100%— rejected as fragile and platform-dependent; hiding the sibling is the simpler, more robust fix.Investigation details
Layout hierarchy when expanded:
View(ReportScreen.tsx:146):flex:1, justifyContent:'flex-end', overflow:'hidden'ReportActionsList(takes flex space)ReportFooterwithchatFooterFullCompose:height:'100%', paddingTop:20The footer's
height: '100%'in a flex context doesn't actually give it 100% of the parent — the flex algorithm distributes space among siblings first. TheReportActionsListconsumes its share, leaving the footer with less than 100%, and its bottom overflows past the parent's bounds whereoverflow: 'hidden'clips it.Inner components (
ComposerInputArea.tsx:26) also setheight: '100%'viachatItemFullComposeRow, cascading the sizing problem down to the text input itself.Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.MobileMage commentedon May 28, 2026
🚨 Edited by proposal-police: This proposal was edited at 2026-05-28 07:05:25 UTC.
Proposal
Please re-state the problem that we are trying to solve in this issue.
When the user types more than three lines into the chat composer and taps the expand icon, the composer enters full-size mode but its content is clipped at the bottom — on web/desktop the composer's bottom border touches the very edge of the viewport (the typing indicator / character-limit row is invisible), and on iOS/Android the bottom of the input area sits beneath the on-screen keyboard. The bug reproduces on staging and production at 9.3.84-0 on every platform listed in the report.
What is the root cause of that problem?
This is a layout-overflow regression introduced by PR #90915 (
refactor: Split ReportActionCompose into more compositional components, merged 2026-05-26, commit6a3c80832c9). Pre-refactor,ReportActionComposerendered a singleReportActionComposeInnerwhose JSX nested the chat-footer indicators (OfflineIndicator,AgentZeroAwareTypingIndicator,ComposerExceededLength) inside the sameOfflineWithFeedbackwhosestylecarriedchatItemFullComposeRow(height: '100%') and whosecontentContainerStylecarriedflex: 1. The input box (flex: 1viachatItemFullComposeBox) and the indicator row (intrinsic ~27px viachatItemComposeSecondaryRow) were therefore siblings of one bounded flex-column parent, so the box grew and the row sat at the bottom — both inside the 100%-height region. The split moved those indicators into a newComposerDefaultFootercomponent, and a follow-up cleanup (commit0eafc2a3fbf, "refactor: remove redundant extra component") then deleted theComposerLayoutwrapper that used to enclose both children, hoistingchatItemFullComposeRowonto the outerViewofComposerInputAreaitself.After that change,
ReportActionComposerenders the two pieces as direct siblings insideComposerProvider, which produces no DOM/native wrapper of its own:App/src/pages/inbox/report/ReportActionCompose/ReportActionCompose.tsx
Lines 27 to 31 in 377d37b
The first sibling,
ComposerInputArea, claimsheight: '100%'(whichchatItemFullComposeRowresolves to viasizing.h100) of its parent — thechatFooterFullComposeViewfromReportFooter, alsoheight: '100%':App/src/pages/inbox/report/ReportActionCompose/ComposerInputArea.tsx
Lines 24 to 27 in 377d37b
The second sibling,
ComposerDefaultFooter(the typing/offline/exceeded-length row), is laid out after that 100%-tall first child in the defaultflexDirection: 'column', so it sits past the bottom of the chat-footer container. The ReportScreen's outer flex column hasoverflow: 'hidden', so on web that overflowed row is clipped and the input box's own bottom border meets the screen edge with no breathing room; on iOS/Android the same overflow plus the missing intrinsic-height "bumper" means the bottom of the input region sits at (or below) the keyboard's top edge, since the only thing that previously kept the input clear of the keyboard was that indicator row taking its 27px share of the bounded region. The "bottom is hidden by keyboard" symptom on native and the "bottom line touches the screen edge" symptom on web are two views of the same regression: an out-of-bounds sibling and no participant in the height division anymore.What changes do you think we should make in order to solve the problem?
Restore the layout invariant the cleanup commit broke: both
ComposerInputAreaandComposerDefaultFootermust share one bounded column whose height ischatItemFullComposeRowin expanded mode, with the input area takingflex: 1and the footer keeping its intrinsic 27px. Concretely, re-introduce a tinyComposerLayout(or equivalently a wrapperViewdirectly inReportActionCompose) that consumesisComposerFullSizefrom Onyx and renders<View style={[isComposerFullSize && styles.chatItemFullComposeRow]}>{children}</View>, and use it inReportActionComposeto wrap<ComposerInputArea /><ComposerDefaultFooter />. Then changeComposerInputArea's own outerViewstyle fromchatItemFullComposeRowtostyles.flex1for theisComposerFullSizecase — its inner column (<ComposerLocalTime />+ the existingflex: 1Viewholding<ComposerContainer />and<ComposerImportedState />) is already correct and doesn't need any other change.After the fix, the inner column inside the new wrapper is:
ComposerInputArea(flex: 1, grows to fill the remaining height) andComposerDefaultFooter(intrinsic ~27px), exactly mirroring the pre-refactorOfflineWithFeedback-children layout that has shipped to production for years. TheEditOnlyReportActionComposecode path is unaffected because it renders<ComposerInputArea />directly inside a sibling<View style={[isComposerFullSize ? styles.chatFooterFullCompose : undefined, styles.mb2]}>inReportFooter(line 163) — that wrapper is already an explicitheight: '100%'flex-column container, soComposerInputArea's newflex: 1resolves correctly without the droppedComposerDefaultFootersibling. No prop or context contract changes are needed, and the non-expanded path is untouched because the new wrapper applies no style whenisComposerFullSizeis false.What alternative solutions did you explore? (Optional)
We considered adding
paddingBottom: insets.bottom + 20tochatFooterFullComposeinReportFooter, which would mask the web "bottom touches the edge" symptom by shrinking the chat-footer content box. We rejected it because the underlying overflow is unchanged —ComposerInputAreawould still claim 100% of that (smaller) content box andComposerDefaultFooterwould still spill past the bottom, so the typing/exceeded-length indicators remain invisible and the mobile keyboard-clip case (which is a layout problem, not a padding one) is not addressed. We also considered movingComposerDefaultFooterinsideComposerInputAreanext toComposerImportedState, but that re-couples the two components and breaks the explicit reason PR #90915 split them apart: lettingEditOnlyReportActionComposerender the input area without the default footer.yusufdeveloper2903 commentedon May 28, 2026
🚨 Edited by proposal-police: This proposal was edited at 2026-05-28 06:56:52 UTC.
Proposal
Please re-state the problem that we are trying to solve in this issue.
When the composer is expanded with the "expand" icon, the bottom of the composer is cut off: on web the last line sits flush against the bottom edge of the screen, and on mobile the bottom of the composer (and its footer row) is hidden behind the keyboard.
What is the root cause of that problem?
In full-size mode the footer row (offline indicator / typing indicator / character-limit warning) is rendered outside the
height: '100%'region instead of sharing space with the composer box.ComposerInputArea's outer wrapper appliesstyles.chatItemFullComposeRow({height: '100%'}) when full-size, so it consumes the entire height of the full-size footer column (chatFooterFullComposeis also{height: '100%'}):App/src/pages/inbox/report/ReportActionCompose/ComposerInputArea.tsx
Lines 23 to 43 in 377d37b
ReportActionComposethen rendersComposerInputAreaandComposerDefaultFooteras siblings, so the footer is laid out after a sibling that already takes 100% of the column height — leaving it zero vertical space and pushing it (and the bottom of the composer box) past the bottom edge:App/src/pages/inbox/report/ReportActionCompose/ReportActionCompose.tsx
Lines 26 to 33 in 377d37b
This is a regression from PR #90915 (
[NoQA] refactor: Split ReportActionCompose into more compositional components, merged 2026-05-26). Before that refactor the footer was rendered inside theOfflineWithFeedbackcontainer (nowComposerContainer), as a sibling of the composer box within the sameflex: 1content area — so the box flex-grew and the footer kept its natural height, both staying visible. The refactor moved the footer out to the top level, breaking that layout.What changes do you think we should make in order to solve the problem?
Render the footer back inside the full-size flex region (inside
ComposerContainer), exactly where it lived before #90915. Pass it as children soEditOnlyReportActionCompose(which has no footer) is unaffected.ReportActionCompose.tsx— move the footer insideComposerInputArea:function ReportActionCompose({reportID}: ReportActionComposeProps) { return ( <ComposerProvider reportID={reportID}> - <ComposerInputArea /> - <ComposerDefaultFooter /> + <ComposerInputArea> + <ComposerDefaultFooter /> + </ComposerInputArea> </ComposerProvider> ); }ComposerInputArea.tsx— accept children and render them insideComposerContainer, as a sibling ofComposerDropZone(the pre-#90915 position):(add
import type {PropsWithChildren} from 'react';). With the footer back inside theflex: 1content area, the composer box grows and the footer keeps its natural height, so the bottom of the composer and its footer stay visible — matching the non-expanded behavior on web, iOS and Android.What alternative solutions did you explore? (Optional)
height: '100%'toflex: 1. Rejected: on native,SwipeableViewwraps the composer in an unstyledView(noflex/height), soflex: 1has no definite parent height to grow into and full-size would collapse. Restoring the footer inside the existingflex: 1region reuses the layout that already worked on every platform.melvin-bot commentedon May 28, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (
External)[-]Chat - Composer field is cut off at the bottom when expanded[/-][+][$250] Chat - Composer field is cut off at the bottom when expanded[/+]melvin-bot commentedon May 28, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022059890385898616348
David-2002065 commentedon May 28, 2026
Proposal
What is the root cause of that problem?
The expanded composer styles set
height: '100%'on three nested flex children of a flex parent — which React Native treats as the measured height of the parent, not the available height after siblings/keyboard are subtracted.The parent container in
ReportScreen.tsx#L142-L155isflex: 1, justifyContent: 'flex-end', overflow: 'hidden', and it renders bothReportActionsListandReportFooteras flex siblings:When the composer expands, three styles all kick in and ask for
height: '100%':chatFooterFullCompose→{ height: '100%', paddingTop: 20 }(nopaddingBottom)chatItemFullComposeRow→{ ...sizing.h100 }chatItemFullComposeBox→{ ...flex.flex1, ...sizing.h100 }100%resolves against the parent's intrinsic height (full report-actions-view-wrapper height), but flex still givesReportActionsListits share of that same height first. So the footer is laid out at "100% of parent" below the actions list, and the bottom slice falls outside the parent — whereoverflow: 'hidden'clips it. On native,KeyboardAvoidingView(enabled inReportScreen.tsx#L114) shrinks the screen by the keyboard height, but the explicit100%doesn't shrink in response, so the keyboard further covers the bottom. On web, the absentpaddingBottomputs the last composer row flush against the viewport edge.This is fundamentally a misuse of
height: '100%'on a flex child — it would beflex: 1if the layout truly meant "take the remaining space."What changes do you think we should make in order to solve the problem?
Two parts. First, when the composer is full-size, stop rendering
ReportActionsListso the footer can legitimately occupy all the flex space (this also avoids wasted re-renders of the message list under an opaque composer):<View style={[styles.flex1, styles.justifyContentEnd, styles.overflowHidden]}> - <ReportActionsList /> + {!isComposerFullSize && <ReportActionsList />} {shouldDeferNonEssentials ? <ReportActionComposePlaceholder /> : <ReportFooter />} </View>(
isComposerFullSizeis already available viauseOnyx(\${ONYXKEYS.COLLECTION.REPORT_IS_COMPOSER_FULL_SIZE}${reportIDFromRoute}`)— same pattern used in [ReportFooter.tsx#L67`](https://github.com/Expensify/App/blob/main/src/pages/inbox/report/ReportFooter.tsx#L67).)Second, replace
height: '100%'withflex: 1in the three full-size styles so the layout cooperates withKeyboardAvoidingViewinstead of fighting it, and add bottom breathing room:chatFooterFullCompose: { - height: '100%', + flex: 1, paddingTop: 20, + paddingBottom: 8, },The same
height: '100%' → flex: 1swap applies tochatItemFullComposeRowandchatItemFullComposeBox(dropsizing.h100, keepflex.flex1). The{height: '100%', maxHeight: 'none'}inline style inComposer/implementation/index.tsx#L351should also become{flex: 1, maxHeight: 'none'}so the<textarea>actually fills its flex parent without hard-coding a percentage.Net effect: when expanded, the footer becomes the only flex child and naturally fills the parent; KAV's keyboard inset shrinks the parent, the footer shrinks with it, and the composer stays fully visible above the keyboard with a small bottom gap on web.
What alternative solutions did you explore? (Optional)
ReportActionsListviadisplay: 'none'instead of conditional render — keeps the actions list mounted (preserves scroll position) but still re-runs its expensive virtualization on each Onyx tick. The user can't see it anyway while expanded, so the perf win of unmounting outweighs scroll restoration; we can persist scroll offset separately if needed.position: 'absolute'overlay for the expanded composer — would solve clipping but breaksKeyboardAvoidingView's padding/height behaviors and safe-area handling. Same reason MelvinBot rejected it.paddingBottomonchatFooterFullComposewithout touching the flex/height issue — masks the web symptom but leaves the native keyboard-cover bug, since the root issue isn't padding, it's theheight: '100%'not shrinking under KAV.20 remaining items
melvin-bot commentedon Jun 2, 2026
@ahmedGaber93 Huh... This is 4 days overdue. Who can take care of this?
neerajbachani commentedon Jun 4, 2026
@ahmedGaber93 friendly bump on this #91927 (comment)
melvin-bot commentedon Jun 4, 2026
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
ahmedGaber93 commentedon Jun 4, 2026
reviewing
ahmedGaber93 commentedon Jun 4, 2026
This issue is fixed on staging by #92207.
Screen.Recording.2026-06-05.at.12.20.43.AM.mov
melvin-bot commentedon Jun 9, 2026
@ahmedGaber93 Eep! 4 days overdue now. Issues have feelings too...
ahmedGaber93 commentedon Jun 11, 2026
Not overdue, asked on slack for closing it 2 days ago.
CC @mallenexpensify #91927 (comment)
melvin-bot commentedon Jun 11, 2026
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
melvin-bot commentedon Jun 11, 2026
@ahmedGaber93 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
mallenexpensify commentedon Jun 15, 2026
Closing as fixed.