[$250] mWeb -Chat - Compose box - Compose box does not increase when user is trying to expand the input field

[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. Go to URL https://staging.new.expensify.com/
2. Log in with any account
3. Navigate to any conversation
4. Focus on the compose box and start typing in a quick manner
5. Type several lines until a button appears to expand the input field

Expected Result:

User can enlarge the compose box and view the text.

Actual Result:

Compose box does not increase when user is trying to expand the input field

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.11.2

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Bug6044941_Screen_Recording_20230506_181042_Chrome.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/~0153ba2368067fa39f
• Upwork Job ID: 1664776867304271872
• Last Price Increase: 2024-06-20

Issue Owner

Current Issue Owner: @

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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

[mallenexpensify]

I was unable to reproduce at first, unless it's supposed to expand more.

2023-05-08_14-40-14.mp4

Then, after, I kept playing around with and I think I maybe/sorta reproduced?

2023-05-08_14-41-35.mp4

[mallenexpensify]

Checking in #QA on what expected behaviour is
https://expensify.slack.com/archives/C9YU7BX5M/p1683582657416369

[isagoico]

When comparing the app behavior with the mWeb behavior I see there's a size difference caused by the fact that the app doesn't have the URL header from mWeb

Nevertheless, mWeb does have a funky behavior. I would expect that the compose box expands a moderate amount when using the resize button. Here's a size comparison when the compose box is expanded and not expanded in iOS, the function even inverts the functionality when the message is large.

Note that the issue is also reproducible in mWeb iOS / Chrome

Regarding the documented behavior of this feature, I looked for the PR that introduced this feature and the behavior in mWeb is different to what is now - Check the videos here #11608

[mallenexpensify]

@aimane-chnaif , since you worked on the PR for this feature, any idea what might be going on? Expanding is def functioning differently that in your screenshots in the OP of the PR.

Thanks @isagoico for the sleuthing, screenshot and link to the PR.

[aimane-chnaif]

My PR is too old.
Recently, we limited composer not to take full height to support emoji suggestions.
This issue is more related to #16446

[mallenexpensify]

Thanks @aimane-chnaif , I commented on that issue, it looks like it might be getting put on hold pending another

[melvin-bot]

@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[mallenexpensify]

Looks like we're holding on the below based on - #16446 (comment)

• [HOLD for payment 2024-06-28] MEDIUM: Make auto-complete component work inline #16078

@aimane-chnaif , that look right?

Bumped to weekly and removed Bug since it's on hold.

[aimane-chnaif]

@aimane-chnaif , that look right?

right

[mallenexpensify]

• [HOLD for payment 2024-06-28] MEDIUM: Make auto-complete component work inline #16078

Looks like the above just hit production!
PR is here

Bumping back to Daily to test on Mon/Tues once back.

[roryabraham]

looks like progress might be accelerating in #16078

[roryabraham]

still on HOLD

[mallenexpensify]

Still holding on the below, not much action the past few weeks.

• [HOLD for payment 2024-06-28] MEDIUM: Make auto-complete component work inline #16078

Added to #vip-vsb cuz it doesn't involve money.

[mallenexpensify]

No update on

• [HOLD for payment 2024-06-28] MEDIUM: Make auto-complete component work inline #16078

[mallenexpensify]

Checking on the issue we're holding on.

• [HOLD for payment 2024-06-28] MEDIUM: Make auto-complete component work inline #16078 (comment)

[melvin-bot]

Upwork job price has been updated to $250

[melvin-bot]

Current assignee @allroundexperts is eligible for the External assigner, not assigning anyone new.

[puneetlath]

Reopening this for proposals. Now that we have inline auto-suggestion, we should be able to make the compose box expand to take up the full available space. And we should be able to have that happen on all platforms.

[puneetlath]

Actually, I think #15596 is the best place to handle this. Going to close this one.