Steps to reproduce
- Type in an emoji such as
- Use arrow-left to move the cursor to the left of the emoji
- Try to insert any character
To see the character I’ve typed
Weird change of color of emoji and extra “box” character
- Operating system: MacOS 10.15.7
- Obsidian version: 0.9.3
unable to replicate. same environment.
LATER EDIT: bug present when skin color is modified on emoji.
What are you using as the emoji picker? The box that appears just faintly at the top of the GIF?
@anon27868835 is the default macos Emoji picker
found out that grapheme cluster are not supported
left Obsidian - right TextEdit
I’m using the emoji picker with the default shortcut (CTRL-⌘-SPACE to pop it up)
But if it’s just me, I don’t know, maybe it’s something about the keyboard I’m using (?)
was able to replicate based on second screen capture - @akaalias used an emoji with different skin color.
so emoji modifiers are not supported. maybe related to grapheme cluster ?
No need to apologize! It’s a good question, how should you have known?
Actually learned a Mac trick from you after all these years – I always use character viewer mode for that control and never paid attention that there was an option to use an insertion mode like you showed in your images above. Works similar to on iOS. Cool
is this still happening with latest version of the installer?
Related to: Gender/skin emoji problems in Editor (Codemirror)
Steps to reproduce
- Insert an emoji character (e.g. )
- Press backspace
- The entire emoji is removed.
This happens for all emojis, not just emojis with modifier sequences.
- You end up with:�
It takes 6 backspaces to delete this character.
Can confirm the problem reported by @liam, same on Windows.
I still see this behavior on Mac with 0.12.13.
CodeMirror 6 has support for navigating around graphemes CodeMirror 6 Reference Manual.
Release notes for CodeMirror 5.59.3 (2021-02-20) also indicate they changed something related to zero-width joiners for rendering multi-character emoji:
though the issue linked above is still open.
the issue hasn’t been fully fixed upstream.
this seems to work fine in the new editor.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.