[HOLD - #11768] [$500] Unable to open chat through search when the browser/app size is decreased - reported by @adeel0202

[mvtglobally]

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. Decrease the width of your browser window to the point in which the chat view is not visible, only the LHN
2. Click on the magnifying glass search icon in the LHN header
3. Click on any chat from the search results and observe that you're navigated back to a view of the LHN and not the view of the chat you just clicked on

Expected Result:

When the screen width on Web/desktop has been decreased to the size of mobile/tablet, it should work in exactly the same way as those devices.

1. Click on the search icon to navigate to the search page
2. Click on any chat from the search results
3. Navigate to the chat view
4. Click the back caret < in the top left of the chat to return to the LHN

Actual Result:

The LHN is in view and not the chat

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web
• Desktop App

Version Number: 1.1.79-11
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Screen.Recording.2022-06-16.at.9.41.42.PM.mov

Upwork URL: https://www.upwork.com/jobs/~010e7681ab13edf3b1
Issue reported by: @adeel0202
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1655398548680369

View all open jobs on GitHub

[melvin-bot]

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

[strepanier03]

Triaging now.

Using Chrome browser and trying multiple different sizes I'm unable to recreate this behavior. Is this specific to a certain browser type @mvtglobally?

[adeel0202]

@strepanier03, it is reproducible in chrome and safari both (I couldn't check on any other browser). It is also reproducible in the desktop app.

[strepanier03]

Hmm, I'll send it on but I can't repro myself in Chrome or Firefox.

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @trjExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[Gonals]

Good candidate for external!

[trjExpensify]

Ah yeah, I can repro this. I misread it initially, but yes.. accessing a chat from the Search page doesn't work. Job on upwork here: https://www.upwork.com/jobs/~010e7681ab13edf3b1

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (Exported)

[trjExpensify]

I caught up with Marc earlier and I'm going to pop the issue on [Hold] & Planning for the time being. We have plans to revisit react-navigation more holistically, so we should account for this issue then to avoid adding any additional workarounds or hacks atop of what is already complex code.

[trjExpensify]

This is held, Melv.

[Santhosh-Sellavel]

on hold

[trjExpensify]

^^ 👋 @Luke9389, has this come off hold or something?

[Luke9389]

OH! huh. Weeeird. I coulda sworn someone commented that this was off hold.

My bad!

[trjExpensify]

Ha, all good!

[trjExpensify]

Updated the title to be more specific that this is held on the Navigation initiative.

[JmillsExpensify]

snagging this as I'm on the tracking issue.

[JmillsExpensify]

See the tracking issue for the latest.

[JmillsExpensify]

Still holding.

[JmillsExpensify]

Still held as this initiative goes through the design process.

[JmillsExpensify]

Still holding on the larger react navigation reboot.

[tgolen]

Is this really a case that we should be supporting? I think we only care about "normally" sized browser windows and mobile web clients. My guess is that at these widths, there is quite a bit more broken than just this navigation issue, and so supporting this browser platform and window size should be regarded as a new feature and not a bug.

[JmillsExpensify]

That's a really great point. I think you're right – to the extent that this also fails the "supported platform" stipulation for bugs as well. I'm actually going to close as a result but anyone from Expensify on this issue can re-open if they feel strongly.