Skip to content

[Due for payment 2026-02-23] [$250] IOU-After editing expense details, page not scrolled and focused to system message #75344

Closed

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: v9.2.59-4
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://github.com/Expensify/Expensify/issues/466788
Email or phone of affected tester (no customers): NA
Issue reported by: Applause Internal Team
Device used: Flip 3 OS15
App Component: Money Requests

Action Performed:

  1. Go to https://staging.new.expensify.com/home
  2. User Logged in
  3. Open 1:1 chat
  4. Submit an expense
  5. Enter description and merchant

Expected Result:

After editing expense details, page must be scrolled and focused to system message.

Actual Result:

After editing expense details, page not scrolled and focused to system message.

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

Bug7006624_1763399108792.Recording__2557.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021995566757747857271
  • Upwork Job ID: 1995566757747857271
  • Last Price Increase: 2025-12-08
  • Automatic offers:
    • situchan | Contributor | 109763284
Issue OwnerCurrent Issue Owner: @johncschuster

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 17, 2025
  2. melvin-bot commented on Nov 17, 2025

    @melvin-bot

    Triggered auto assignment to @johncschuster (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.

  3. melvin-bot commented on Nov 29, 2025

    @melvin-bot

    @johncschuster 10 days overdue. Is anyone even seeing these? Hello?

  4. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    @johncschuster 12 days overdue now... This issue's end is nigh!

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Dec 1, 2025
  6. changed the title [-]IOU-After editing expense details, page not scrolled and focused to system message[/-] [+][$250] IOU-After editing expense details, page not scrolled and focused to system message[/+] on Dec 1, 2025
  7. melvin-bot commented on Dec 1, 2025

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 1, 2025
  9. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (External)

  10. 51 remaining items

  11. johncschuster commented on Feb 17, 2026

    @johncschuster
    Contributor

    Payment Summary

    Contributor: @situchan paid $250 via Upwork ✅
    Contributor+: @nkdengineer due $250 via NewDot

  12. johncschuster commented on Feb 23, 2026

    @johncschuster
    Contributor

    @blimpich / @trjExpensify / @nkdengineer can you take a look at the proposed regression test steps below to make sure this is correct?

    Regression Test Proposal

    Precondition:

    • User is logged in to New Expensify
    • User has a 1:1 chat or workspace chat with at least one submitted expense that has multiple editable fields (merchant, description, category, tag, date, amount, etc.)
    • The expense report chat has enough messages that the chat is scrollable (i.e., the system messages and expense details are not all visible at once)

    Test:

    Scenario 1: Editing a single expense field does not auto-scroll

    1. Open a chat that contains a submitted expense
    2. Scroll up in the chat so the most recent messages are NOT visible (scroll position is in the middle of the chat)
    3. Tap on the expense to open the expense RHP (right-hand panel)
    4. Edit the Merchant field and save
    5. Verify that the chat does not auto-scroll to the bottom after saving
    6. Verify that the user's scroll position in the RHP remains stable (user should still be looking at the expense details, not scrolled away)

    Scenario 2: Editing multiple expense fields in succession

    1. Open a chat that contains a submitted expense
    2. Tap on the expense to open the expense RHP
    3. Edit the Merchant field and save
    4. Verify the RHP does not scroll away — the expense form fields remain visible
    5. Immediately edit the Description field and save
    6. Verify the RHP does not scroll away
    7. Edit the Category field (if available on the policy) and save
    8. Verify the RHP still does not scroll away
    9. Verify the user can continue editing fields without having to scroll back up after each edit

    Scenario 3: System messages are still appended correctly

    1. Open a chat that contains a submitted expense
    2. Edit the Merchant field on the expense and save
    3. Scroll down to the bottom of the chat
    4. Verify that a system message indicating the merchant was changed is present at the bottom of the chat
    5. Verify the system message content is correct (reflects the field change)

    Scenario 4: Cross-platform verification

    • Repeat Scenarios 1 and 2 on:
      • Android (native app)
      • Android (mWeb Chrome)
      • iOS (native app)
      • iOS (mWeb Safari)
      • macOS (Chrome/Safari)

    Do we agree 👍 or 👎

  13. blimpich commented on Feb 23, 2026

    @blimpich
    Contributor

    I think that's correct but Tom should be final check 👍

  14. trjExpensify commented on Feb 24, 2026

    @trjExpensify
    Contributor

    Bit schlopppy and verbose to me, in all honesty. Would have been good to take a pass after Melvlad. I think it can be condensed to:

    Precondition:

    • Enable and configure categories, tags, and tax on a workspace to make the expense form long.

    Steps

    1. Create a couple of expenses, filling out categories, tag, and tax values on the expenses.
    2. Go to the expense report > submit it
    3. Open one of the expenses on the report
    4. Verify the scroll position is at the top of the expense form
    5. Edit the category value
    6. Verify the scroll position doesn't change upon editing the category value

    That would cover it, IMO. Example:

    2026-02-24_00-43-28.mp4

    Then, importantly. @m-natarajan and Applause, let's have this replace this test case.

  15. johncschuster commented on Feb 24, 2026

    @johncschuster
    Contributor

    Thanks, @trjExpensify! I'll make sure it's clear that we need to replace the test case you've linked.

  16. johncschuster commented on Feb 24, 2026

    @johncschuster
    Contributor

    @nkdengineer please request payment, here!

  17. m-natarajan commented on Feb 24, 2026

    @m-natarajan

    @trjExpensify Created new test case for this and removed the referenced one from testing

  18. trjExpensify commented on Feb 25, 2026

    @trjExpensify
    Contributor

    Thank you!

  19. twisterdotcom commented on Feb 25, 2026

    @twisterdotcom
    Contributor

    @nkdengineer has submitted payment for this report on ND here.

    SO: https://stackoverflowteams.com/c/expensify/questions/7582

    Zapier Logs Run ID: 00040eee-92c6-aab0-2a0a-8e85ea44db34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions