[wp-trac] [WordPress Trac] #64318: ↗ should not be replaced by Twemoji
WordPress Trac
noreply at wordpress.org
Mon Feb 9 19:18:47 UTC 2026
#64318: ↗ should not be replaced by Twemoji
--------------------------+---------------------
Reporter: Joen | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 7.0
Component: Emoji | Version: 4.2
Severity: normal | Resolution:
Keywords: has-patch | Focuses:
--------------------------+---------------------
Comment (by siliconforks):
Replying to [comment:17 westonruter]:
> The problem is existing content out there that doesn't have U+FE0E,
right? Existing content expecting the text presentation unexpectedly gets
the emoji presentation when upgradinging Twemoji.
Yes, but it could also be the other way around - the user might have
originally wanted the graphical emoji presentation, and now it could get
changed to the simple text presentation.
> So would a new filter be required for `the_content` to inject this
U+FE0E after the set of characters that we determine? But then this
wouldn't really be any different than the JS-based exclusion? Both are
programmatic means to the same end.
That has the same problem - there's no way to be certain what the user
actually intended. What if the user actually wanted the graphical emoji
presentation? Then injecting U+FE0E would be wrong.
The JavaScript solution in [https://github.com/WordPress/wordpress-
develop/pull/10603 PR #10603] (to avoid using Twemoji for certain
characters) might be reasonable as a "best guess" for what the user
wanted. But ultimately I don't think this is something that can entirely
be fixed in WordPress (or in Twemoji). Ideally the operating system's
character picker (or wherever the user got the character from) should
insert the correct Unicode sequence, either `U+2197 U+FE0E` (for the
simple text presentation) or `U+2197 U+FE0F` (for the graphical emoji),
depending on what the user actually chose.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64318#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list