[$250] mWeb- The edit composer is not focused

[mitarachim]

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

---

Version Number: 9.0.97-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #55438
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Device used: iPhone 13 18.2.1/Safari
App Component: Chat Report View

Action Performed:

1. Navigate to https://staging.new.expensify.com
2. Open any chat.
   3.Send a message containing at least 2 lines of emojis and no text. For example:
   🙃
   🙃
   4.Long tap or right-click on the message you just sent and select "Edit comment".

Expected Result:

After taping on the message and selecting "Edit comment", the edit composer is focused.
The edit composer appears smoothly without a jump.
The edit composer is fully displayed, e.g. the bottom part is not hidden under the main composer.

Actual Result:

After tapping on the message and selecting "Edit comment", the edit composer is not focused. And after tapping the composer, it is not focused in the end of the message.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6740219_1739328694114.ScreenRecording_02-11-2025_21-47-50_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021891343482527010932
• Upwork Job ID: 1891343482527010932
• Last Price Increase: 2025-02-17

Issue Owner

Current Issue Owner: @jjcoffee

[melvin-bot]

Triggered auto assignment to @RachCHopkins (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[RachCHopkins]

@mitarachim @MariaHCD I haven't had an issue like this before where a regression is caught like this. I'm not sure what the steps are. I can't seem to find any stack overflow that covers this scenario.

[MariaHCD]

@RachCHopkins Since this is a regression from #55438, it will be handled as part of #55068

[MariaHCD]

cc: @CyberAndrii @alitoshmatov

[CyberAndrii]

I don't think this has anything to do with #55438 as it hasn't been deployed to production yet, and this issue is reproducible in prod.

[RachCHopkins]

@CyberAndrii that's exactly why I am super confused with what is happening here. Should we just remove reference to that PR and treat it as a standalone bug?

[CyberAndrii]

Yeah

[RachCHopkins]

Can repro. Very weird.

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

@jjcoffee, @RachCHopkins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[jjcoffee]

Waiting for proposals!