-
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
LHN - LHN scrolls to the top when navigating between tabs #56323
Comments
Triggered auto assignment to @MarioExpensify ( |
Triggered auto assignment to @muttmuure ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
Scroll to the top all the time on Prod bandicam.2025-02-04.12-57-55-122.mp4 |
It seems we're even "slightly better" in Staging than in Prod. I'm removing the Deploy Blocker. It seems @rezkiy37 is already aware of the issue and is working to find a solution for browsers. CC: @puneetlath |
Yes, I am working on it in the scope of #53605. |
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: 9.0.94-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #55486
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 10/ Chrome, Samsung Galaxy A12/Android 13
App Component: Left Hand Navigation (LHN)
Action Performed:
Expected Result:
LHN always scrolls on the correct previous position.
Actual Result:
LHN alternate between scrolling to the correct previous position and to the top.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6733004_1738665227026.Recording__126.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: