Web - Task - The message entry field in a task disappears when the focus is removed from the tab

[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. Open https://staging.new.expensify.com/
2. Navigate to a Group Chat
3. Click on the + in the compose box
4. Select "Assign task"
5. Enter a Title and a Description
6. Do not assign any group member
7. Create the task
8. Take the focus off the tab (go to another chat room, open a new tab)
9. Go back to the created task

Expected Result:

The message entry field in a task should not disappear when you remove focus from the tab.

Actual Result:

The message entry field in a task disappears when the focus is removed from the tab.

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.3.46-0
Reproducible in staging?: y
Reproducible in production?: n
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

Bug6142622_Recording__117.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 @francoisl (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[manan-upadhyay]

If the input is not rendered conditionally, this issue might be caused by the height of the container and content overflow issue. In the first case, the render conditions needs to be checked, else we might just need to update some CSS

[melvin-bot]

📣 @manan-upadhyay! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
2. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
3. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[manan-upadhyay]

Contributor details
Your Expensify account email: upadhyaymanan01@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~0122e0ed8ca6eca7fa

[melvin-bot]

✅ Contributor details stored successfully. Thank you for contributing to Expensify!

[francoisl]

this issue might be caused by the height of the container and content overflow issue.

@manan-upadhyay to clarify, are you saying there's already a known issue with content overflow?

Anyway, I'm unable to reproduce the issue on staging and dev, are you?

app_23675.mov

[marcaaron]

FWIW - I also can't repro this one.