Chat - Edit composer is slightly higher than the main composer

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.58-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #98781
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Chat Report View

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an empty report.
4. Open the report.
5. Send a message.
6. Press keyboard up button.

Expected Result:

Edit composer will have the same height as the main composer.

Actual Result:

Edit composer is slightly higher than the main composer.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7238846_1787278699461.10.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7238846

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/8948c433bf8ca933f9df9fafc1501493e3144436e1789b472e92633d83e6106a

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #98781

[melvin-bot]

@mollfpr @Eskalifer1 you have been assigned to this deploy blocker because you reviewed the offending PR: #98781

[melvin-bot]

@shawnborton you have been assigned to this deploy blocker because you authored the offending PR: #98781

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.