-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for #39198] Chat - Chat does not scroll to the latest messages when new message sent #40094
Comments
Triggered auto assignment to @greg-schroeder ( |
We think this issue might be related to the #vip-vsb. |
This issue maybe fixed in this PR #39685. |
Agreed, I'll hold this until then and this may be resolved |
PR was deployed to prod, will ask QA to retest |
Pinged QA |
Issue not reproducible during KI retests. (First week) |
Issue not reproducible during KI retests. (Second week) |
closing per QA review |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.62-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4488827&group_by=cases:section_id&group_order=asc&group_id=306202
Email or phone of affected tester (no customers): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition: User should be Signed Out
Expected Result:
Chat should be scrolled to latest messages when user sent a new message
Actual Result:
The chat does not scroll to the bottom when the user sends a message in step 5. However, when the user navigates to the LHN and then returns in step7-8, the chat scrolls to the bottom after the message is sent. This issue occurs when the user navigates to an uncached chat after signing in.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6445467_1712815152526.RPReplay_Final1712815103.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: