[HOLD for payment 2024-05-08] Web - Chat - Composer jumps when entering first emoji

[m-natarajan]

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: 1.4.58.0
Reproducible in staging?: Yes
Reproducible in production?: No
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
Expensify/Expensify Issue URL:
Issue reported by: Applause Internal Team
Slack conversation:

Action Performed:

1.Go to staging.new.expensify.com/
2.Go to any chat
3.Enter an emoji

Expected Result:

The composer will not jump

Actual Result:

The composer jumps when entering the first emoji

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

20240329_233527.mp4

Add any screenshot/video evidence

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @slafortune

[melvin-bot]

Triggered auto assignment to @francoisl (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @slafortune (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[github-actions]

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

[m-natarajan]

We think this bug might be related to #vip-vsb

[m-natarajan]

@slafortune FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[francoisl]

I can repro, this comes from the Live Markdown preview #38152. Not sure if it's worth being a blocker though. Looks like there are other open blockers due to the markdown preview anyway, let's see if we end up reverting it.

cc @thienlnam for visibility.

[thienlnam]

Not a blocker, I've added it to the main tracking list with a high priority

[BartoszGrajdek]

Hi! I'm Bartosz from SWM / react-native-live-markdown team - I'll be taking a look into what's happening here later today! 👀

[slafortune]

@BartoszGrajdek I've assigned you 👍

[melvin-bot]

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

[melvin-bot]

@slafortune @thienlnam @BartoszGrajdek this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[Skalakid]

I opened PR with the fix for review :D

[slafortune]

@thienlnam @Skalakid @BartoszGrajdek I'll be out until 4/22, not assigning another BZ since this is in a good place with you all to keep it moving forward 👍

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.68-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fix jumping composer when entering emojis or markdown text #40128

If no regressions arise, payment will be issued on 2024-05-08. 🎊

For reference, here are some details about the assignees on this issue:

• @BartoszGrajdek does not require payment (Contractor)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@thienlnam] The PR that introduced the bug has been identified. Link to the PR:
• [@thienlnam] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@thienlnam] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@BartoszGrajdek] Determine if we should create a regression test for this bug.
• [@BartoszGrajdek] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@slafortune] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[slafortune]

@BartoszGrajdek Can you complete the checklist above?

[slafortune]

@BartoszGrajdek does not require payment (Contractor)

[BartoszGrajdek]

@BartoszGrajdek Can you complete the checklist above?

I believe @Skalakid was the one who actually fixed this

[melvin-bot]

Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

[fedirjh]

cc @slafortune Could you please reopen this issue to handle the payment for the C+ review? Thank you.

[slafortune]

Shoot! I am sorry about that @fedirjh ! Offer sent here - https://www.upwork.com/nx/wm/offer/102318459

[fedirjh]

@slafortune Thank you. Accepted.

[slafortune]

Paid