[$250] [Search v2.2] Chat is scrolled to the bottom when refreshing the page

[IuliiaHerets]

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: v9.0.31-0
Reproducible in staging?: Y
Reproducible in production?: N/A
Email or phone of affected tester (no customers): applausetester+shsb22ertt@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Log in to Newdot
2. Go to Search option from bottom tab
3. Click on "Chat" type from LHP
4. Click on any message which is not at the bottom of a chat report
5. When the report view is opened in RHP refresh the browser
6. Now notice how the chat report is scrolled to the bottom

Expected Result:

The chat report in RHP is not scrolled down to the bottom and stays in the same report action opened before refreshing the page

Actual Result:

The chat report in RHP is scrolled down to the bottom and user has to scroll up to find the chat report opened before refreshing the page

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6597778_1725902355625.2024-09-09_19_35_43.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021833217065296959946
• Upwork Job ID: 1833217065296959946
• Last Price Increase: 2024-09-16
• Automatic offers:
• ikevin127 | Contributor | 103886648
• huult | Contributor | 104028956

Issue Owner

Current Issue Owner: @rojiphil

[melvin-bot]

Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

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

[IuliiaHerets]

We think that this bug might be related to #wave-control

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

[luacmartins]

I'll take this since it's part of Search