Web -Chat -Unable to scroll large text in expanded compose box with large text

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Go to URL https://staging.new.expensify.com/
2. Login with any account
3. Navigate to any chat
4. Add large text
5. Make a field extension

Expected Result:

Large texts must be scrolled in the extension field

Actual Result:

Unable to scroll large text in open format in compose box

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web
• Desktop

Version Number: 1.2.16-2
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Bug5778195_Recording__1554.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[techievivek]

This indeed is a problem. Once we expand the compose box, we can no longer scroll.

[techievivek]

Passing it to external contributors to have a look. My guess is it is some styling issue.

[melvin-bot]

Triggered auto assignment to @sonialiap (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External)

[melvin-bot]

Triggered auto assignment to @luacmartins (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[thesahindia]

Will be fixed by #11608

[techievivek]

I am keeping it on HOLD because I can see that the PR above will fix this issue. Sorry for the pings.

[melvin-bot]

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

[techievivek]

#11885 (comment) We already have a fix for it so once it is deployed we will be good to close this issue.

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[techievivek]

Not overdue. We have put it on hold because we have already fixed this here.

[techievivek]

Not overdue.

[techievivek]

Not overdue, the issue is on hold as we have a fix here.

[JmillsExpensify]

We should assign someone from Bug Zero to test this one now that #11437 is merged.

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[JmillsExpensify]

@techievivek I think we're good to close this issue now, right?

[techievivek]

Yep, We are safe to close this now.