[HOLD for payment 2024-04-09] [HOLD for payment 2024-04-05] Chat - Emoji tab opens at lower level, Change default skin tone not accessible for an attachment

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 1.4.57-2
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
Email or phone of affected tester (no customers): applausetester+kia1@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Navigate to staging.new.expensify.com
2. Go to any chat - 1:1 DM, #admins room
3. Tap on + icon in composer >> select add attachment >> upload attachment
4. Hover over attachment & select add reaction option from action menu
5. Scroll down the emoji panel

Expected Result:

Emoji tab should open at the top level, so that "Change default skin tone" option in emoji panel should be accessible in 100% zoom for an attachment when selecting the add reaction option from action menu

Actual Result:

1. Emoji tab opens at the same level as the attachment message & hence "Change default skin tone" option in emoji panel not accessible in 100% zoom for an attachment when selecting the add reaction option from action menu
   Also, some of the flag emojis not accessible as well
2. Issue happens for an attachment saved just above the composer field

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

Bug6430381_1711641233117.Recording__110.mp4

View all open jobs on GitHub

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

[melvin-bot]

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

[lanitochka17]

We think that this bug might be related to #vip-vsp

[lanitochka17]

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

[lanitochka17]

Production:

Recording.111.mp4

[francoisl]

I can repro on staging but not in dev, I think this is already fixed. I see 2 new PRs that modified the emoji popover got merged but are not on staging yet, figuring out which one fixes it and will request a CP.

[francoisl]

Ok yeah, pretty sure #39143 fixes this. There's already a CP running for it, I'll test again when it's deployed.

[francoisl]

Confirmed fixed on staging now.