Skip to content

[Awaiting Payment March 20th] [$500] Report - The conversation scrolls to the beginning when you open the settings menu #35763

Closed

Description

@izarutskaya

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.4.36-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):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation:

Action Performed:

  1. Open https://staging.new.expensify.com/
  2. Log in under your HT account A
  3. Navigate to a conversation with more messages
  4. Scroll to the top of your conversation history so that the last message is not visible
  5. Open settings via avatar
  6. Close the setting via the "Back" arrow

Expected Result:

When you close the settings menu, the conversation should not restart and scroll back to the beginning.

Actual Result:

The conversation scrolls to the beginning when you open the settings menu

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

Bug6366093_1706977070977.Recording__1272.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0154928522b8004b1d
  • Upwork Job ID: 1753894702380920832
  • Last Price Increase: 2024-03-18
  • Automatic offers:
    • akinwale | Reviewer | 0
Issue OwnerCurrent Issue Owner: @trjExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 3, 2024
  2. changed the title [-]Report - The conversation scrolls to the beginning when you open the settings menu[/-] [+][$500] Report - The conversation scrolls to the beginning when you open the settings menu[/+] on Feb 3, 2024
  3. melvin-bot commented on Feb 3, 2024

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 3, 2024
  5. melvin-bot commented on Feb 3, 2024

    @melvin-bot

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

  6. melvin-bot commented on Feb 3, 2024

    @melvin-bot

    Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  7. github-actions commented on Feb 3, 2024

    @github-actions
    Contributor

    👋 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.
  8. 91 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 19, 2024
  10. akinwale commented on Mar 19, 2024

    @akinwale
    Contributor

    @trjExpensify #36888 was already a known issue prior to the PR being submitted as the performance problem was identified beforehand (context), so I think one regression deduction applies here.

  11. adamgrzybowski commented on Mar 19, 2024

    @adamgrzybowski
    Contributor

    @trjExpensify

    Ah okay cool, so we have an issue for that PR to progress it. Would be good if it's extendable to cover the report screen cases, but we can look into that over there.

    I would merge the PR for scroll on the HOME page and ask somebody from SWM to use this code to create similar solution for the report screen scroll.

    Do you want to create and issue for that?

  12. mountiny commented on Mar 20, 2024

    @mountiny
    Contributor

    Seems like this got handled well. We got an issue for the bottom tabs and PR to fix it going on

    @trjExpensify with the chats I guess it depends, you can see Slack keeps the position. WhatsApp desktop does not though, I think we can explore how to solve this but we need to make sure it will solve well and would not hurt performance even if we would store the position for many reports (or put some limit on 10 latest visited reports for example.)

  13. trjExpensify commented on Mar 20, 2024

    @trjExpensify
    Contributor

    @trjExpensify #36888 was already a known issue prior to the PR being submitted as the performance problem was identified beforehand (#35763 (comment)), so I think one regression deduction applies here.

    Ah okay, got it. Cool, updated the payment summary. Offers sent to you both!

  14. changed the title [-][$500] Report - The conversation scrolls to the beginning when you open the settings menu[/-] [+][Awaiting Payment March 20th] [$500] Report - The conversation scrolls to the beginning when you open the settings menu[/+] on Mar 20, 2024
  15. akinwale commented on Mar 20, 2024

    @akinwale
    Contributor

    @trjExpensify Accepted. Thanks!

  16. trjExpensify commented on Mar 20, 2024

    @trjExpensify
    Contributor

    @trjExpensify with the chats I guess it depends, you can see Slack keeps the position. WhatsApp desktop does not though, I think we can explore how to solve this but we need to make sure it will solve well and would not hurt performance even if we would store the position for many reports (or put some limit on 10 latest visited reports for example.)

    Yeah, maybe we can bring this out for a discussion in somewhere like #vip-vsb to decide what we want to do. I agree we don't want to take a performance hit, but I do think keeping the position will be desirable when we use this a lot for all of our business chat purposes where you're switching a lot.

  17. trjExpensify commented on Mar 20, 2024

    @trjExpensify
    Contributor

    @trjExpensify Accepted. Thanks!

    Paid!

  18. trjExpensify commented on Mar 22, 2024

    @trjExpensify
    Contributor

    @sahilnagpal26 waiting for you to accept the offer.

  19. trjExpensify commented on Mar 25, 2024

    @trjExpensify
    Contributor

    @sahilnagpal26 paid. Closing!

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions