Skip to content

regression: skin-toned emoji not enlarged when sent alone - #41515

Merged
dionisio-bot[bot] merged 1 commit into
release-8.7.0from
fix/skin-tone-emoji-not-enlarged
Jul 22, 2026
Merged

regression: skin-toned emoji not enlarged when sent alone#41515
dionisio-bot[bot] merged 1 commit into
release-8.7.0from
fix/skin-tone-emoji-not-enlarged

Conversation

@ricardogarim

@ricardogarim ricardogarim commented Jul 22, 2026

Copy link
Copy Markdown
Member

Proposed changes (including videos or screenshots)

Skin-toned emoji variants (e.g. high_five ✋🏽) stayed small when sent as an emoji-only message, while the default version (✋) was correctly enlarged.

Root cause: A message made only of emoji is enlarged only when it is recognized as a single emoji. A skin-toned emoji is actually two parts — a base emoji plus a separate skin-tone modifier — that must be joined into one.

Emoji are spread across several Unicode ranges, and the message parser only joined the skin-tone modifier for some of them. For two of those ranges (which include hands like ✋ ✌ ✍ ☝ ⛹), the modifier was not joined, so a skin-toned emoji was read as two things: the base emoji plus a leftover skin-tone swatch. The result was a big default-colored hand next to a tiny swatch, instead of one enlarged skin-toned emoji. The plain version (✋) worked because it has no modifier to lose.

Fix: Allow those two ranges to join the skin-tone modifier too, like the others already did. Now a skin-toned emoji is read as a single emoji and enlarges correctly. Emoji without a skin tone are unaffected.

Issue(s)

Steps to test or reproduce

  1. Send high_five (✋) alone → enlarged.
  2. Pick a skin tone and send high_five with different tone (✋🏽) alone.
  3. Before: stays small. After: enlarged with the correct skin tone.

Further comments

Review in cubic

Summary by CodeRabbit

  • Bug Fixes

    • Improved recognition of additional Unicode emojis with skin-tone modifiers.
    • Correctly parses combined emoji sequences and emojis embedded within surrounding text.
  • Tests

    • Added coverage for hand, arm, and activity emojis, including modified and concatenated forms.

@ricardogarim ricardogarim added this to the 8.7.0 milestone Jul 22, 2026
@dionisio-bot

dionisio-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Looks like this PR is ready to merge! 🎉
If you have any trouble, please check the PR guidelines

@changeset-bot

changeset-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: bacca02

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0a4499f8-f31d-43ae-9b54-dcda011cbe1b

📥 Commits

Reviewing files that changed from the base of the PR and between e106db1 and bacca02.

📒 Files selected for processing (2)
  • packages/message-parser/src/grammar.pegjs
  • packages/message-parser/tests/emoji.test.ts
🚧 Files skipped from review as they are similar to previous changes (2)
  • packages/message-parser/src/grammar.pegjs
  • packages/message-parser/tests/emoji.test.ts
📜 Recent review details
⏰ Context from checks skipped due to timeout. (4)
  • GitHub Check: 📦 Build Packages
  • GitHub Check: CodeQL-Build
  • GitHub Check: Hacktron Security Check
  • GitHub Check: CodeQL-Build

Walkthrough

The message parser now applies Fitzpatrick modifiers to additional Unicode emoji categories. Tests cover standalone, concatenated, and inline skin-toned emoji parsing.

Changes

Unicode emoji parsing

Layer / File(s) Summary
Apply skin-tone modifiers across emoji categories
packages/message-parser/src/grammar.pegjs, packages/message-parser/tests/emoji.test.ts
The grammar includes dingbat and miscellaneous symbol emoji in the modifier-capable group, with tests for standalone, concatenated, and inline variants.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

Suggested labels: type: bug

Suggested reviewers: cardoso

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the fix for single skin-toned emoji being parsed incorrectly and not enlarged.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • CORE-2456: Request failed with status code 401

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ricardogarim
ricardogarim marked this pull request as ready for review July 22, 2026 13:41
@ricardogarim ricardogarim changed the title fix: skin-toned emoji not enlarged when sent alone regression: skin-toned emoji not enlarged when sent alone Jul 22, 2026

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

Re-trigger cubic

@ricardogarim
ricardogarim force-pushed the fix/skin-tone-emoji-not-enlarged branch from e106db1 to bacca02 Compare July 22, 2026 15:53
@abhinavkrin abhinavkrin added the stat: QA assured Means it has been tested and approved by a company insider label Jul 22, 2026
@dionisio-bot dionisio-bot Bot added the stat: ready to merge PR tested and approved waiting for merge label Jul 22, 2026
@dionisio-bot
dionisio-bot Bot merged commit c774ae1 into release-8.7.0 Jul 22, 2026
54 checks passed
@dionisio-bot
dionisio-bot Bot deleted the fix/skin-tone-emoji-not-enlarged branch July 22, 2026 21:39
@codecov

codecov Bot commented Jul 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.60%. Comparing base (8d4507d) to head (bacca02).
⚠️ Report is 8 commits behind head on release-8.7.0.

Additional details and impacted files

Impacted file tree graph

@@                Coverage Diff                @@
##           release-8.7.0   #41515      +/-   ##
=================================================
+ Coverage          68.58%   68.60%   +0.01%     
=================================================
  Files               4134     4135       +1     
  Lines             160802   160814      +12     
  Branches           29244    29236       -8     
=================================================
+ Hits              110294   110332      +38     
+ Misses             45403    45364      -39     
- Partials            5105     5118      +13     
Flag Coverage Δ
e2e 58.86% <ø> (-0.02%) ⬇️
e2e-api 45.62% <ø> (+0.29%) ⬆️
unit 70.54% <100.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stat: QA assured Means it has been tested and approved by a company insider stat: ready to merge PR tested and approved waiting for merge type: bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants