Markdown footnotes backlinks arrow

The arrow used in footnotes backlinks is being rendered as an emoji on some browsers (for me: desktop Chrome, iOS Chrome, iOS Safari), but not on others (desktop Firefox, desktop Safari).

We don’t believe so. Different browsers do not necessarily render content the same way.

The browsers all end up showing arrows. Is there something particularly wrong you’re seeing in the presentation?

Would it be possible to change the icon/character used for the backlinks in an “elegant” way?

That seems like a valid solution. If that is not satisfactory for you, you may be able to use the following filter to create something more desirable:

https://developer.jetpack.com/hooks/wpcom_markdown_transform_post/

If you need assistance with these types of modifications, we suggest looking into a service that can help you customize your site, such as the WordPress Professional Network:

https://jetpack.pro/

We hope that helps, and let us know if you have any more questions.

Thanks for the reply! I will take a look at the filter.

The browsers all end up showing arrows. Is there something particularly wrong you’re seeing in the presentation?

I just find it wrong to see an emoji instead of the actual character, because we don’t expect to see an emoji used for the backlink text in a footnote. It’s distracting and just seems plain wrong. And it’s ugly.

Often, the emoji colours will not fit the design used on the website.

Also, it’s inconsistent. It would be OK to have a slightly different arrow rendered in every browser, or even a different emoji (but only if all browsers rendered the emoji, which is not happening).

Now, some browsers show the emoji, while others show the arrow character.

The MarkdownExtra parser apparently has a setting to avoid the emoji. Wouldn’t it be possible to use this with Jetpack Markdown?

https://michelf.ca/projects/php-markdown/configuration/#markdown-extra

fn_backlink_html = "↩︎"

HTML content for a footnote backlink. The ︎ suffix in the default value is there to avoid the curled arrow being rendered as an emoji on mobile devices, but it might cause an unrecognized character to appear on older browsers.

Edit: Huh, using the code ticks in the blockquote above does not avoid the & # 8617 (without spaces) from being rendered as an emoji…

• This reply was modified 7 years, 1 month ago by Argumentum.
• This reply was modified 7 years, 1 month ago by Argumentum. Reason: formatting

Hi,

I’ve tested with and without Jetpack (also Jetpack Markdown), it’s still displaying the emoji.

As I see, the emoji appearance is handled by the WordPress core.

If you do not want to use emoji, you can have a look at this quick guide
https://kinsta.com/knowledgebase/disable-emojis-wordpress/

Cheers,

Hi,

Thanks for testing and replying here. It is a pity the results were a bit disappointing, but now it is clear this is more a WordPress-related issue.

Best,