You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
Using this issue as a catch-all to ensure things are captured. Feel free to break out into multiple issues with better priorities.
Since we switched to use the font based Twemoji implementation on Riot Web (& plan to use it on Riot Android), some concerns and thoughts have arisen:
Despite our best efforts (a) some browsers/OS's still fail to always to render emoji (b) we've observed at least on macOS that some browser plugins can cause Riot Web to display native OS emoji intermittently. To ensure consistency for emoji verification, should we bundle SVG's for the 64 emoji we use?
For technical reasons, we don't plan to use Twemoji on iOS. We should validate the emoji we've picked are easily identifiable between native Apple emoji & Twemoji. From there, we should consider (a) refining the selection or (b) including Twemoji on iOS for verification only for consistency across platforms.
We should validate we're happy with how distinct each emoji is in Twemoji— for example banana and moon have a very similar silhouette, and strawberry and apple are easily mistakable at a glance. Again, we may want to refine our selection.
The text was updated successfully, but these errors were encountered:
nadonomy
changed the title
Implications of new twemoji implementation on emoji verification
Twemoji verification issues
May 31, 2019
Using this issue as a catch-all to ensure things are captured. Feel free to break out into multiple issues with better priorities.
Since we switched to use the font based Twemoji implementation on Riot Web (& plan to use it on Riot Android), some concerns and thoughts have arisen:
The text was updated successfully, but these errors were encountered: