There are 5 updates.
 
 
Confluence / cid:jira-generated-image-avatar-e112d15c-eff2-4b6b-9da4-1f2014092308 CONFLUENCE-388 Closed

Handle new Confluence cloud ac:emoticon tags in which ac:emoji-fallback doesn't contain an actual emoji anymore

 
View issue   ·   Add comment
 

5 updates

 
cid:jira-generated-image-avatar-ccac8139-d7aa-4351-b65b-edebbd894473 Changes by Raphaël Jakse on 29/Jan/25 15:02
 
Fix Version: 9.76.2
Description: See [https://forum.xwiki.org/t/confluence-import-broken-emoticon-import-with-new-confluence-format/16354]

Formerly, we could rely (or at least we thought we could rely) on {{ac:emoji-fallback}} containing the actual emoji, like in the following:
{code:java}
<ac:emoticon ac:name="smile" ac:emoji-shortname=":slight_smile:" ac:emoji-id="1f642" ac:emoji-fallback="🙂" /
>
{code}
(and, by the way, on ac:emoji-id containing the hexa code of the emoji)

Now we can't, as code like this exists:
{code:java}
<ac:emoticon ac:name="cross" ac:emoji-shortname=":cross_mark:" ac:emoji-id="atlassian-cross_mark" ac:emoji-fallback=":cross_mark:" />
{code}
We need to rely on ac:name first, and only fall back on other options if we don't know the emoji.
Assignee: Raphaël Jakse
Resolution: Fixed
Status: Open Closed