mWeb - Chat - Keyboard stays open in details page

[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!

---

Issue found when executing PR #19428

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Login with any account
3. Open group > send message > react with 2 or more accounts
4. Hover over the members in the list
5. Click on the user
6. Notice it should open the user detail page

Expected Result:

The keyboard collapses when you go to the details page

Actual Result:

Keyboard stays open in details page

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.19.2

Reproducible in staging?: yes

Reproducible in production?: ew feature

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

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

Notes/Photos/Videos: Any additional supporting documentation

https://platform.applause.com/services/links/v1/external/e840decd40039193643fd7e4d4ff03d875118d416c86dfb1beda4c7d773a8779

https://platform.applause.com/services/links/v1/external/bba2d198b3761a3e16ff1e2bd872ff6519a6850d0db02e615edaab641688f571

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b5bed8070cd317b5
• Upwork Job ID: 1672335678406971392
• Last Price Increase: 2023-06-23

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[joekaufmanexpensify]

@kbecciv as it stands right now, I cannot reproduce this based on the steps included above. The keyboard is closing for me when I do this. However, the steps above were not 100% clear to me, and it's difficult to validate whether the exact actions I took are correct, because there is no video on the bug report.

2023-05-26_15-46-17.mp4

[joekaufmanexpensify]

I'm going to assign this back to you for now. If the video I posted above is not what you intended with the above reproduction steps, could you please add a video showing the exact actions you took to encounter this issue?
If my video is correct, and you can no longer reproduce this, please close the issue.

If you add a video to this issue between 2023-05-27 - 2023-06-05, please remove and re-add the bug label so someone else is assigned, as I'll be OOO then. Then, please assign me as an additional assignee too.

Otherwise, please feel free to just re-assign me. Thanks!

[melvin-bot]

@kbecciv Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@kbecciv Eep! 4 days overdue now. Issues have feelings too...

[kbecciv]

@joekaufmanexpensify Checking with QA team, will update you shortly