#52852 closed enhancement (fixed)
Update Twemoji for 5.8
Reported by: | desrosj | Owned by: | desrosj |
---|---|---|---|
Milestone: | 5.8 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Emoji | Keywords: | has-patch has-unit-tests |
Focuses: | Cc: |
Description (last modified by )
A new version of Twemoji, v13.0.2 is now available.
This is a minor update that does not introduce any new Emoji, but instead fixes and refines 14 preexisting ones.
Here is a summary of some changes:
- Cricket: the colors have been adjusted to improve readability on small screens and to prevent confusion with other Emoji that had a similar color.
- T-Rex: The color and posture of the T-Rex has been adjusted.
- Portuguese flag: A line within the flag's circle has been corrected.
- Thai flag: The proportions of the stripes for this flag have been corrected.
- Fox face: The symmetry has been improved.
- Transgender flag: The lines have been updated to prevent small gaps between stripes from showing when rendered with antialiasing.
- Rolling on the floor laughing: Adjusted to be less exaggerated and appear more natural.
Since no source code changes will result from updating the library's version in package.json
and the meanings of the Emoji have not been altered, the current 13.0.1
folder on the CDN can be updated with the latest versions. All users for sites running WordPress 5.6 or higher will see the new Emoji immediately, or when the caching for the respective files expires.
Attachments (3)
Change History (20)
#4
@
4 years ago
@Otto42 would you be able to update the CDN versions on .org? The latest versions are here: https://github.com/twitter/twemoji/releases/tag/v13.0.2.
This would be similar to the update in [dotorg:15520] for #48293.
#5
@
4 years ago
@desrosj So, do we want to introduce a 13.0.2 directory for these, or just update the existing 13.0.1 directory with the new icons?
#6
@
4 years ago
Let's just continue using the current 13.0.1
folder please!
Since no changes are required in the Core code base, this will allow us to push the update out to everyone right away (no need to wait for 5.8).
#7
@
4 years ago
- Resolution set to fixed
- Status changed from assigned to closed
Files updated in [dotorg:17102].
Files modified:
72x72/1f1f5-1f1f9.png
72x72/1f1f9-1f1ed.png
72x72/1f3af.png
72x72/1f489.png
72x72/1f606.png
72x72/1f616.png
72x72/1f61d.png
72x72/1f923.png
72x72/1f927.png
72x72/1f92e.png
72x72/1f98a.png
72x72/1f996.png
72x72/1f997.png
svg/1f1f5-1f1f9.svg
svg/1f1f9-1f1ed.svg
svg/1f3af.svg
svg/1f3f3-fe0f-200d-26a7-fe0f.svg
svg/1f489.svg
svg/1f606.svg
svg/1f616.svg
svg/1f61d.svg
svg/1f923.svg
svg/1f927.svg
svg/1f92e.svg
svg/1f98a.svg
svg/1f996.svg
svg/1f997.svg
#8
@
4 years ago
- Keywords has-patch has-screenshots removed
- Resolution fixed deleted
- Status changed from closed to reopened
Twemoji has released version 13.1.0, which has a few new emoji. See https://github.com/twitter/twemoji/releases/tag/v13.1.0
tl;dr: Various bearded figure modifications (neutral, man, woman bearded options), a lot of variations of skin tones + people kissing, with five totally new emoji (heart on fire, bandaged heart, face with spiral eyes, face in clouds, face exhaling.
What do y'all think about continuing to use the 13.0.1 folder or switching to a new 13.1.0? In 13.0.2, we kept the same dir even though the syringe emoji changed a fair amount (blood vs empty, to align with what the other vendors are doing to make the emoji character work for vaccines too).
With that change, I would think a new folder (and the patch acts as such).
This ticket was mentioned in PR #1314 on WordPress/wordpress-develop by kraftbj.
4 years ago
#9
- Keywords has-patch has-unit-tests added
- Update to Twemoji 13.1.0
- Update detection script
Twitter has released a new version of Twemoji. Let's update our version.
Trac ticket: https://core.trac.wordpress.org/ticket/52852
#10
@
4 years ago
Aside: I'm not sure if this counts as a feature change (and thus too late for 5.8) or not. If it's too late for 5.8, just let me know and I'll re-open a 5.9 Twemoji ticket.
#11
@
4 years ago
- Keywords commit added
What do y'all think about continuing to use the 13.0.1 folder or switching to a new 13.1.0?
I think it may be best to introduce a new 13.1.0
folder on the CDN. While the syringe did change quite a bit, I felt it was OK to push out because, in my opinion, it would have a potentially positive impact.
That said, all of the other updates in 13.0.2
were relatively minor, and no new Emoji were introduced. Any time new emoji are introduced, it's probably best to have a new folder.
Aside: I'm not sure if this counts as a feature change (and thus too late for 5.8) or not.
There are probably sensible arguments for both sides of this. I think it's reasonable to include this update. The messaging would become pretty confusing if we need to say "Twemoji was updated, but only to 13.0.2
, and 13.1.0
will be included in the next release." It's more clear to just say "updated to the latest version."
Also, since we're creating a new folder on the CDN, it won't be possible to push further minor refinements (should they happen) to users until 5.9 is released if this update is not included.
Your PR looks good to me @kraftbj! Happy to commit it once we're able to push the new folder to the CDN.
#12
@
3 years ago
- Keywords commit removed
Just noting that latest 13.1.0 version of Twemoji was committed in [dotor:17419] and pushed to the CDN. Props @Otto42 for that.
In my pre-commit testing of this, I'm not seeing the new emoji being loaded properly. I haven't had a chance to dig deeper, but the files are accessible on the CDN. The front end replacement is just not happening.
#13
@
3 years ago
@desrosj -- I'll look into it too. What operating system are you using? The replacement won't occur if your OS already supports it. macOS added this in 11.3 per https://www.theverge.com/2021/4/26/22404124/mac-macos-update-11-3-security-ios-app-m1-gaming-controller-music
#14
@
3 years ago
Ah! I think I found what the issue was.
In the JavaScript to detect whether newer Emoji are supported, the characters in the first set were incorrect. They were listed as 0xD83C, 0xDD25
, which actually corresponds to the parenthesized Latin capital letter V.
The fire emoji is 0xD83D, 0xDD25
, which was changed in set2
but not set1
. The 0xD83C
was the first character of the baby bottle Emoji (0xD83C, 0xDF7C
) used in the last version. I think that was just missed in the PR attached. I've pushed this change to the PR to verify with the tests.
@kraftbj could you give the updated PR some testing today?
#15
@
3 years ago
@desrosj Thanks for catching that. It was, indeed, me testing out the patch without having everything committed. With your commit, it is rendering it like I'd expect.
In 50548: