This issue has been created
There are 2 updates.
 
 
Confluence / cid:jira-generated-image-avatar-a813c316-5f59-4135-9d18-d466b301a872 CONFLUENCE-388 Open

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

 
View issue   ·   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-55a2b837-5d00-4928-a291-3b39f25abe74 Raphaël Jakse created this issue on 29/Jan/25 14:38
 
Summary: Handle new Confluence cloud ac:emoticon tags in which ac:emoji-fallback don't contain an actual emoji anymore
Issue Type: cid:jira-generated-image-avatar-a813c316-5f59-4135-9d18-d466b301a872 Bug
Affects Versions: 9.76.2
Assignee: Unassigned
Components: XML
Created: 29/Jan/25 14:38
Priority: cid:jira-generated-image-static-major-1ec64fb9-a544-4608-8294-c1638c6cf10c Major
Reporter: Raphaël Jakse
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:

<ac:emoticon ac:name="smile" ac:emoji-shortname=":slight_smile:" ac:emoji-id="1f642" ac:emoji-fallback="🙂" /

(and, by the way, on ac:emoji-id containing the hexa code of the emoji)

Now we can't, as code like this exists:

<ac:emoticon ac:name="cross" ac:emoji-shortname=":cross_mark:" ac:emoji-id="atlassian-cross_mark" ac:emoji-fallback=":cross_mark:" />

We need to rely on ac:name first, and only fall back on other options if we don't know the emoji.

 
 

2 updates

 
cid:jira-generated-image-avatar-55a2b837-5d00-4928-a291-3b39f25abe74 Changes by Raphaël Jakse on 29/Jan/25 14:39
 
Summary: Handle new Confluence cloud ac:emoticon tags in which ac:emoji-fallback don doesn 't contain an actual emoji anymore
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.