-
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
[$500] [Wave Collect] [Ideal Nav] Going back to Workspace Settings page resets the selected setting item #35613
Comments
Triggered auto assignment to @MitchExpensify ( |
The attached video is unrelated. This is the bug Screen.Recording.2024-02-02.at.5.28.54.PM.mov |
Job added to Upwork: https://www.upwork.com/jobs/~01e287e0122a51dbb7 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Going back to Workspace Settings page resets the selected setting item What is the root cause of that problem?the selected/focused item depends on the active route
and we currently just navigate to overview by default so overview is always opened and focused. App/src/libs/Navigation/AppNavigator/createCustomBottomTabNavigator/BottomTabBar.tsx Lines 70 to 71 in 3a610af
What changes do you think we should make in order to solve the problem?We need to save in App/src/pages/workspace/WorkspaceInitialPage.js Lines 211 to 212 in 3a610af
whenever setting is pressed we will navigate to the saved last menu item here. App/src/libs/Navigation/AppNavigator/createCustomBottomTabNavigator/BottomTabBar.tsx Lines 70 to 71 in 3a610af
What alternative solutions did you explore? (Optional)Optionally we can also find the last menu item from the route history (latest workspace setting page opened for the workspace) and navigate to it here App/src/libs/Navigation/AppNavigator/createCustomBottomTabNavigator/BottomTabBar.tsx Lines 70 to 71 in 3a610af
but this will not work when the user has refreshed after navigating away from the workspace settings page |
Why should it open the same workspace settings tab when you leave to "chat" and then return by clicking "Settings" @hayata-suenaga ? Aren't you opening Settings for the first time everytime you click "Settings"? (In which case "Overview" makes sense to me every time you click "Settings") |
ops thank you for pointing that out 🙇
I'll ask about this in Slack if this is the intended design 👍 asking about this here |
Cool, following along there 👁️ |
Hey! I’m Wojtek from Software Mansion, an expert agency, and I’d like to work on this issue. |
moving this over to SWMs hands for focused and urgent resolution 🙇 |
@MitchExpensify, @WojtekBoman, @thesahindia, @hayata-suenaga Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@WojtekBoman will work on this |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 ( |
@cubuspl42 @WojtekBoman from an expert agency is going to open a PR for this issue |
I'm on it 👍 |
@cubuspl42, @MitchExpensify, @WojtekBoman, @hayata-suenaga Whoops! This issue is 2 days overdue. Let's get this updated quick! |
The PR was merged but it caused a regression. Wojciech is going to work on a PR to fix the regression. |
The fix PR was merged |
@cubuspl42, @MitchExpensify, @WojtekBoman, @hayata-suenaga Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
the pr was merged and we're just waiting for payment after regression period is over |
@cubuspl42, @MitchExpensify, @WojtekBoman, @hayata-suenaga Whoops! This issue is 2 days overdue. Let's get this updated quick! |
reviewing label was not automatically removed when the PR was merged 🤔 |
Issue not reproducible during KI retests. (First week) |
I confirmed this is not reproducible. Closing the issue |
Action Performed:
Overview
Chat
icon to go to Chat pageExpected Result:
The previously selected item should be focused when going back to Workspace Settings page.
Actual Result:
Check the focus is on Overview`, not the item you selected previously.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
video -> #35613 (comment)
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: