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
[Due for payment 2025-03-21] [$250] Chat - Unable to scroll to the top when scrolling up at moderate speed #58160
Version Number: 9.1.11-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):applausetester+h9ne229@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Chat Report View
Action Performed:
Go to staging.new.expensify.com
Go to chat.
Send a few attachments (at least three on web & desktop, at least four on Android & iOS) to the chat so that the chat is scrollable.
Scroll up at a moderate speed (not too fast and not too slow).
Expected Result:
Chat will be scrolled to the top smoothly.
Actual Result:
The chat is stuck in the middle when scrolling up at a moderate speed.
👋 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.
@MariaHCD I think this is definitely an issue - I can't reproduce the issue exactly as Applause have written the steps, but I noticed that when I scroll up, I can never reach the top. It's just a constant scroll up, like in this video:
@ZhenjaHorbach@jliexpensify@ZhenjaHorbach The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
The fix was made by the developer of the PR which caused regression
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Test:
Open App
Go to chat
Send a few attachments (at least three on web & desktop, at least four on Android & iOS) to the chat so that the chat is scrollable.
Scroll up at a moderate speed (not too fast and not too slow)
Activity
melvin-bot commentedon Mar 11, 2025
Triggered auto assignment to @MariaHCD (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 11, 2025
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Mar 11, 2025
Triggered auto assignment to @jliexpensify (
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.github-actions commentedon Mar 11, 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:
jliexpensify commentedon Mar 11, 2025
@MariaHCD I think this is definitely an issue - I can't reproduce the issue exactly as Applause have written the steps, but I noticed that when I scroll up, I can never reach the top. It's just a constant scroll up, like in this video:
2025-03-11_15-21-56.mp4
MariaHCD commentedon Mar 11, 2025
Interestingly, I was able to reproduce the issue once on staging web but then I refreshed and I can't seem to reproduce it anymore:
Screen.Recording.2025-03-11.at.11.06.47.AM.mov
I wasn't able to reproduce on staging desktop at all 🤔
Screen.Recording.2025-03-11.at.11.08.17.AM.mov
41 remaining items
melvin-bot commentedon Mar 14, 2025
@ZhenjaHorbach @jliexpensify @ZhenjaHorbach The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
martasudol commentedon Mar 18, 2025
Hey, the fix has already been merged. Is there anything else needed from my side, or can we close this issue?
ZhenjaHorbach commentedon Mar 18, 2025
Remaining payment and regression period until 21.03 !
jliexpensify commentedon Mar 18, 2025
@ZhenjaHorbach any checklist needed?
jliexpensify commentedon Mar 18, 2025
Payment Summary
https://www.upwork.com/jobs/~021899378621478971427
ZhenjaHorbach commentedon Mar 18, 2025
I think it will be useful
I will fill out the checklist tomorrow !
melvin-bot commentedon Mar 19, 2025
jliexpensify commentedon Mar 19, 2025
Hmm @ZhenjaHorbach - is there a regression here?
jasperhuangg commentedon Mar 19, 2025
Sorry, there's no regression here. I mistakenly marked this PR as causing a deploy blocker.
jliexpensify commentedon Mar 19, 2025
Np, ty Jasper!
ZhenjaHorbach commentedon Mar 19, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
The fix was made by the developer of the PR which caused regression
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Test:
Do we agree 👍 or 👎
jliexpensify commentedon Mar 21, 2025
Paid, and job closed!