[HOLD for payment 2024-02-09] [$500] mWEb/Safari - Chat - Header not anchored at top in conversation when compose box is focused

[lanitochka17]

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: .1.3.45-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): applausetester+1117ck@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Tap on FAB button >> Start Chat option
2. Start 1:1 DM with several messages already between users
3. Send messages (Note: Header section anchored at top)
4. Tap back button to go to LHN
5. Tap FAB button >> Start Chat with same user
6. Click in composer (Note : Header not anchored at top)

Expected Result:

Header should be anchored at top in conversation when compose box is focused

Actual Result:

Header not anchored at top in conversation when compose box is focused

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6364031_1706818525652.Video2.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01dd20f281b9038937
• Upwork Job ID: 1753198333098303488
• Last Price Increase: 2024-02-01
• Automatic offers:
• situchan | Reviewer | 28135933
• mkhutornyi | Contributor | 28135934

[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.

[melvin-bot]

Triggered auto assignment to @srikarparsi (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[lanitochka17]

Production:

Bug6364031_1706818525640.RPReplay_Final1706811929.2.mp4

[francoisl]

Possibly the same root cause as #35593

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01dd20f281b9038937