[HOLD #11768] Web- Chat - Transition using the back button does not work correctly

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Log in with an account that has multiple chats
3. Open any chat
4. Open a different chat
5. And any other again
6. Click the browser's back button

Expected Result:

The transition back must be consecutive in the reverse order

Actual Result:

Transition using the back button does not work correctly

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.88.13

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5691702_Recording__1505.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[AndrewGable]

Seems like this happens on production, so I don't think it should be a deploy blocker.

[marcaaron]

I am pretty sure this is a duplicate and related to some issues we have that are on hold so going to put this one on HOLD as well.

[melvin-bot]

This issue has not been updated in over 15 days. eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[melvin-bot]

Triggered auto assignment to @johncschuster (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[JmillsExpensify]

Still held on the larger navigation re-write.

[JmillsExpensify]

Still on hold for navigation.

[JmillsExpensify]

Still on hold for navigation. No ETA.

[JmillsExpensify]

Same same.

[JmillsExpensify]

Still on hold.

[JmillsExpensify]

Still on hold

[JmillsExpensify]

Coming off hold very soon!

[JmillsExpensify]

Working on testing this week.

[JmillsExpensify]

Still trying to make time. Low priority.

[JmillsExpensify]

The transition back must be consecutive in the reverse order

Just re-tested and this works perfectly!

[JmillsExpensify]

Reported by QA so nothing due for issue reporting.