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
Chat - Chat Page does not scroll to the bottom when receiving new message #34279
Version Number: 1.4.24-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:
Sign in on account A on web
Sign in on account B on another device
Account A and B should have previous conversation which is scrollable on the chat page
While chat is open on account A on web and is scrolled to the bottom send a message to account A from account B
Observe the chat page on account A
Expected Result:
The chat page should scroll down to the bottom to show the newly received comment
Actual Result:
The chat stays at the same position after new messages arrive
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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
github-actions commentedon Jan 10, 2024
👋 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:
melvin-bot commentedon Jan 10, 2024
Triggered auto assignment to @marcaaron (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.situchan commentedon Jan 10, 2024
Seems like same root cause as #34240
roryabraham commentedon Jan 10, 2024
agree, should be fixed by #34244
marcaaron commentedon Jan 11, 2024
Think this one can be closed out now.