Issue Summary

Legacy Editor - ac:emoji-fallback not rendered in migrated pages | The customer wants a fallback mechanism for unsupported emojis in the cloud editor.

Specifically, when emoticons like ac:name="backhand index pointing right" are not found, they want to use the ac:emoji-fallback attribute to display an alternative character instead of showing an error.

This issue is specific to pages migrated from on-premise to the cloud, where certain emojis are not supported by design.

Steps to Reproduce

1. Migrate a page from on-premise to the cloud that uses the syntax <ac:emoticon ac:name="backhand index pointing right" ac:emoji-id="1f449" ac:emoji-fallback="👉" />.
2. Open the page in the cloud editor.
3. Observe that the ac:emoji-fallback is not rendered, and an error is shown instead.

Expected Results

The editor should use the ac:emoji-fallback attribute to display the alternative character when the emoji name is not found.

Actual Results

The editor does not render the ac:emoji-fallback attribute, resulting in an error display.

Workaround

We can still use the following syntax on the page storage format however the editor will render blue-start and the view will render the fallback
<ac:emoticon ac:name="blue-star" ac:emoji-shortname=":point_right:" ac:emoji-id="1f449" ac:emoji-fallback="👉" />