Skip to content

mWeb - Chat not autoscrolled to bottom after rejecting expense on report and returning to chat #70573

@nlemma

Description

@nlemma

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

  1. Open the staging.new.expensify.com website.
  2. Open any workspace chat.
  3. Create two manual expenses.
  4. Open the report of the just created expenses.
  5. Tap on "Submit"
  6. Open any of the two expenses.
  7. Tap on "More" and select "Reject"
  8. Enter any reason and reject the expense.
  9. Once redirected to report again, return to chat.
  10. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6945091_1757945430289.Auto.mp4

View all open jobs on GitHub

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions