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
mWeb - Chat not autoscrolled to bottom after rejecting expense on report and returning to chat #70573
Version Number: 9.2.14-1 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from TestRail:#62787 Email or phone of affected tester (no customers):ibellicotest+1786@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb) App Component: Chat Report View
Action Performed:
Prerequisite: Account has at least one workspace created.
Prerequisite 2: Delayed submissions and approvals enabled.
Open the staging.new.expensify.com website.
Open any workspace chat.
Create two manual expenses.
Open the report of the just created expenses.
Tap on "Submit"
Open any of the two expenses.
Tap on "More" and select "Reject"
Enter any reason and reject the expense.
Once redirected to report again, return to chat.
Note that rejected expense, that was moved to a different report, is not visible, as the chat is not autoscrolled to the bottom.
Expected Result:
Chat should be automatically autoscrolled to the bottom after rejecting an expense on a report with more than one expense, and returning to chat.
Actual Result:
After rejecting an expense on a report with more than one expense, and returning to chat, the rejected expense, that was now moved to a new report, is not visible, as the chat is not automatically scrolled to the bottom.
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Sep 15, 2025
Triggered auto assignment to @laurenreidexpensify (
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 commentedon Sep 15, 2025
Triggered auto assignment to @Beamanator (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 15, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 15, 2025
👋 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:
2 remaining items
mananjadhav commentedon Sep 16, 2025
We're only adding a new action and nothing else is changed in the logic for scroll. This might be the same for other actions as well.
lakchote commentedon Sep 16, 2025
Should be behind a beta see #70579 (comment)
truph01 commentedon Sep 16, 2025
I can't reproduce this bug:
Screen.Recording.2025-09-16.at.15.22.48.mov
@mananjadhav What about you?
IuliiaHerets commentedon Sep 16, 2025
The issue is no longer reproducible on mWeb.
Device: Samsung A15, Android 15
Build: 9.2.14-4-staging
-1586932619758845202mweb__70573.mp4
mananjadhav commentedon Sep 16, 2025
I can't reproduce it either.
Beamanator commentedon Sep 16, 2025
yep cuz we put reject behind a beta :D
mananjadhav commentedon Sep 16, 2025
No I meant by commenting the beta as well 😅
Beamanator commentedon Sep 16, 2025
aah nice!! we also CP'd a few fixes, did you write that PR? 🤣
mananjadhav commentedon Sep 16, 2025
Nothing related to this 😅
garrettmknight commentedon Sep 17, 2025
I can't repro either. Closing.
Screen.Recording.2025-09-17.at.5.46.00.PM.mov