[HOLD #40412] Live MD - No top margin for only emojis inside the expanded compose box

[lanitochka17]

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.63-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: N/A
Issue reported by: Applause - Internal Team

Action Performed:

1. Navigate to staging.new.expensify.com
2. Open any chat
3. Add an emoji only
4. Enter a new line
5. Expand the compose box

Expected Result:

There is a margin between the emoji inside the compose box and the top border of the compose box

Actual Result:

There is space between the emoji inside the compose box and the top border of the compose box

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

Add any screenshot/video evidence

Bug6453394_1713431122292.bandicam_2024-04-18_12-00-18-497.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @roryabraham (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ 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.

[lanitochka17]

@roryabraham 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

[MahmudjonToraqulov]

This will be fixed with this Proposal

[MahmudjonToraqulov]

Result

[roryabraham]

calling this NAB and putting it on HOLD for #40412 as it appears to share the same root cause.

[melvin-bot]

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

[roryabraham]

Still on HOLD - making this a weekly while we wait for #40412 to land

[roryabraham]

Still on HOLD

[roryabraham]

Still on HOLD

[roryabraham]

still on HOLD

[melvin-bot]

This issue has not been updated in over 15 days. @roryabraham eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[roryabraham]

Verified that this is fixed