macOS Non-Latin IME input issue

[lifehome]

Issue Summary

When you tries to input non-latin glyphs(e.g., Chinese characters) into the editor, either plain text or with addon like Markdown block or HTML block, it always breaks.

Not only cannot type properly, but typing with IME also breaks the entire blog post...
It is very frustrating to "undo" and "redo" all the typings and things...

Security concerns

I am aware that Ghost probably using mobiledoc for a while? I am not yet having the time to trace down the rabbit hole, but I do see there are CVE for that specific library, and I am really concerned if I should continue the use of Ghost...?

To Reproduce

1. Create a new post
2. Start typing some non-latin characters

Screencast

ghost_ime_issue.mp4

Technical details:

• Ghost Version: 4.14.0
  • Docker tag: ghost:alpine(ghost@sha256:7f22aaffb1e46803280101e22f54c19d958405d25faf0bc0035ef63ce08b21f7)
• Node Version: 14.17.6
• Browser/OS:
  • Client side: macOS 11.6 on Firefox 92.0
  • Server side: Arch Linux on Linux kernel 5.13.13
• Database: Probably SQLite...?

Possible related issue (and probably not getting fixed on the root cause?)

• Not possible to toggle with arrow keys before having finalized japanese input codemirror/codemirror5#4096
• Post editor has problems with non-latin IME character input #12820
• [Bug Fixed] Long-existing non-latin IME bug fixed, please update & merge latest mobiledoc-kit #12268
• IME Bug: Ghost suffering IME bug for 2 years and Never Fix it #11460
• Editor: IME input problem #9801
• Incorrect Japanese IME popup position #9289
• Cursor doesn't work well with Bopomofo IME #9012
• Japanese text issue on the new WYSIWYG editor #8319

[Pathsis]

The problem of typing CJK texts with initials seems to have been solved in the current version. Do you mean such an issue?

[ErisDS]

Hi there 👋

I suspect this is an upstream issue in mobiledoc-kit. So that we can be sure would you be able to test out the same key strokes in the mobiledoc kit demo here:

https://bustle.github.io/mobiledoc-kit/demo/

Please let us know if you can see the same issue when typing there or not.

Also, in terms of us being able to reproduce the issue, it would be very handy if you could provide the exact reproduction steps, including exactly which keys are being pressed and their order, plus which main keyboard language you are using.

If you're able to, screencasts with the keyboard viewer present on mac, or that otherwise show the exact keys pressed would be very helpful.

[github-actions]

Note from our bot: The needs info label has been added to this issue. Updating your original issue with more details is great, but won't notify us, so please make sure you leave a comment so that we can see when you've updated us.

[github-actions]

Hey @lifehome 👋

Our team needed some more info to get to the bottom of this, however we've not heard back from you. We're going to close this for now, but let us know if you manage to dig up some more info and we'll reopen.