We're finding that emoji-mart is providing the text presentation sequence rather than the emoji presentation sequence for certain emoji, yielding very different emoji in browsers that support both.
For example, :zap: which is 26a1, should actually be 26a1-fe0f to display properly as emoji in all environments. Notice the difference in WKWebView (Mac OS embedded browser). The top example is taken from emoji-mart (native), the bottom is typed using the built-in emoji keyboard and gives the proper emoji presentation sequence:
Meanwhile, other emoji are properly defined with the correct presentation sequence, as you can see from the data here (v14):
We're finding that emoji-mart is providing the text presentation sequence rather than the emoji presentation sequence for certain emoji, yielding very different emoji in browsers that support both.
For example,
:zap:which is26a1, should actually be26a1-fe0fto display properly as emoji in all environments. Notice the difference in WKWebView (Mac OS embedded browser). The top example is taken from emoji-mart (native), the bottom is typed using the built-in emoji keyboard and gives the proper emoji presentation sequence:Meanwhile, other emoji are properly defined with the correct presentation sequence, as you can see from the data here (v14):