[HOLD for payment 2023-04-03] WEB - Chat - Draft text is not cleared but the compose box is still focused

[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 #15650

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Login with any account
3. Go to any chat
4. Write some text in the compose box
5. Press Esc
6. Verify that the draft text is cleared but the compose box is still focused
7. Repeat Steps 3,4,5

Expected Result:

Draft text is cleared but the compose box is still focused

Actual Result:

If you repeat the steps 3,4,5 several times, then the comment does not disappear.

Workaround:

Unknown

Platforms:

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

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

Version Number: 1.2.80.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:

Email or phone of affected tester (no customers):

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5967861_Recording__346.mp4

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/~012df6b447b406c99c
• Upwork Job ID: 1633544219615494144
• Last Price Increase: 2023-03-08

[MelvinBot]

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

[MelvinBot]

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

[tjferriss]

@luacmartins this issue appears like it could be the same as #15597. What do you think?

I was able to reproduce the issue:

Screen.Recording.2023-03-08.at.9.42.54.AM.mov

[luacmartins]

I see. This is related to the PR linked in the OP. Seems like the debounce we have on the composer box is putting the text back in it. I can take a look at this.

[MelvinBot]

Job added to Upwork: https://www.upwork.com/jobs/~012df6b447b406c99c

[MelvinBot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @Santhosh-Sellavel (Internal)