Edit Comment - After editing the comment, main compose box is not focused

[isagoico]

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

---

Expected Result:

Main compose box should be focused so the user can start typing without needing to manually focus.

Actual Result:

Main compose box is not focused after editing a comment.

Action Performed:

1. Log in to e.cash
2. Navigate to a conversation
3. Send a message.
4. Right click on the message and click on edit comment
5. Edit the comment a bit and click enter

Workaround:

User has to manually focus the compose box.

Platform:

Where is this issue occurring?

Web ✔️
iOS ✔️
Android ✔️
Desktop App (Unable to check)
Mobile Web ✔️

Version Number: 1.0.60-0

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

Notes/Photos/Videos: Any additional supporting documentation

Recording.188.mp4

Expensify/Expensify Issue URL:

View all open jobs on Upwork

---

From @roryabraham https://expensify.slack.com/archives/C01GTK53T8Q/p1622578939426200

After editing a message, the main ReportActionCompose is not refocused.

[MelvinBot]

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

[mountiny]

Update: I will work on the setup of E.cash with Mark Louis today and then I will try to tackle this issue.

[mountiny]

Update: Still struggling to set up the Android, I will continue tomorrow.

[mountiny]

Update: I was trying to figure out how to focus the compose box after an event happening in different component, I haven't managed yet, I will continue later.

[mountiny]

Update: Today i was solely working on other issue. Hopefully tomorrow I will have time for this one.

[mountiny]

This PR and other metioned issues there could be helpful.

[parasharrajat]

@mountiny Have you found a solution to this? Otherwise I would like to take upon it. I have planned a solution that will cover this issue as well. Thanks.

[mountiny]

@parasharrajat hey! I wanted to work on this one today. I was trying to find some quick solution but we will most likely have to elevate this to global storage as otherwise you cannot really control components in different parts of the DOM tree.

Have you already started your PR for the other issues your solution should solve?

[parasharrajat]

@mountiny
Yes I have started the PR but I am yet to implement a solution which can be used to fix this issue as well. We have planned everything and today it would be done. Here is the issue #3017.

[mountiny]

@parasharrajat Great! Seems like you are on it then! Try to chip in a comment here as well as you will progress your work on the other issue. Thanks!

[parasharrajat]

@mountiny PR is ready #3017.