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
Version Number: 9.0.5-2 Reproducible in staging?: y Reproducible in production?: y Issue found when executing PR:#41962 Issue reported by: Applause - Internal Team
Click on the "New message" badge that appeared at the top of the chat
Confirm the page scrolls to the bottom of the comment history
Click on the second link sent on step 5.
Click on the "New message" badge once again
Expected Result:
The report page scrolls down to the bottom of the comment history
Actual Result:
The report page doesn't scroll down to the bottom of the comment history after clicking on the second link, and this time clicking on the first link and then clicking on the new message badge no longer scrolls to the bottom of the comment history as well.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
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: 9.0.5-2
Reproducible in staging?: y
Reproducible in production?: y
Issue found when executing PR: #41962
Issue reported by: Applause - Internal Team
Action Performed:
)
Expected Result:
The report page scrolls down to the bottom of the comment history
Actual Result:
The report page doesn't scroll down to the bottom of the comment history after clicking on the second link, and this time clicking on the first link and then clicking on the new message badge no longer scrolls to the bottom of the comment history as well.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6535893_1720445935785.bandicam_2024-07-08_16-28-48-145.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @RachCHopkins