Editor: IME input problem

[minwe]

This is an issue in the upstream mobiledoc-kit library and the underlying problem is being tracked in multiple places on that repo, with the two most prominent issues being:

• Input on android and IME has a bug when typing first char bustle/mobiledoc-kit#589
• Entering logograms issues in macOS bustle/mobiledoc-kit#548

Please direct any further discussion or PRs to the mobiledoc-kit repo.

---

Issue Summary

As the screen recording above shown, I want to input 你好 using Chinese Pinyin Input method of Mac OS X on the start of line，I type nihao，then got i好n.

The first typed n is inserted after cursor.

To Reproduce

1. Switch Input method to non-latin languages, e.g. Chinese Pinyin Input method, Japanese
2. Type some letter like nihao, expect to get 你好, but get i好n

It is the bug of Mobiledoc-Kit, can reproduce on https://bustle.github.io/mobiledoc-kit/demo/, too.

Technical details:

• OS: Mac OS X, v10.13.6
• Node Version: v8.11.1
• Ghost-CLI Version: 1.9.0
• Browser/OS: Chrome/67.0.3396.99
• Database: sqlite3

[kevinansfield]

Hey @minwe 👋 Thanks for the report. Unfortunately this is a known issue, it's being tracked in the upstream mobiledoc-kit repo in bustle/mobiledoc-kit#548 and I believe the underlying problem is similar to this issue bustle/mobiledoc-kit#589.

[minwe]

Yes, this is same as bustle/mobiledoc-kit#548.

It maybe caused by composition event (more about omposition event: http://blog.evanyou.me/2014/01/03/composition-event/)

I'll check mobiledoc-kit source code later.

[kevinansfield]

It would be great if you were able to look. None of the core team use IME input so it's difficult to find and debug these issues.

bustle/mobiledoc-kit#589 is a good read as I believe it's likely the root cause and has more info in it. Unless you are seeing the same buggy behaviour when not typing the first word in a blank paragraph?

[minwe]

@kevinansfield It always happens when typing the first word of paragraph, headline, list and other block element.

I'm looking at the issues you mentioned above, but have no idea so far.

[taking]

Korean has the same problem.

[S8Cloud]

It seems using IME in markdown section or title section works fine. Hoping there is a option to disable Koeing Editor before it can work along with IME.

[buchijiang]

So when can it solved?

[vikaspotluri123]

@buchijiang whenever the upstream issue (bustle/mobiledoc-kit#548) is solved - there's no explicit timeline publicly available

[buchijiang]

@vikaspotluri123 OK,i know and thanks for answer

[Windfarer]

There should be an alternative editor to this issue.

[S8Cloud]

Agree with @Windfarer , old Markdown editor works well and for now I have to fall back to Ghost 1.25.5

[soulteary]

@buchijiang whenever the upstream issue (bustle/mobiledoc-kit#548) is solved - there's no explicit timeline publicly available

Thanks.

TLDR;

But the mobiledoc-kit's Maintainers don't seem to merge it, so I created new repo for publish NPM repo: @bugfix/mobiledoc-kit

• source code here: https://github.com/soulteary/mobiledoc-kit
• changes: soulteary/mobiledoc-kit@47ac016

Just change the package.json deps @tryghost/mobiledoc-kit to @bugfix/mobiledoc-kit which in the ghost-admin project, and rebuild the assets with prod env, everything is fine.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[miaowing]

When to fix it in master?

[taking]

Is it technology that can not be fixed?

[kevinansfield]

This is an issue in the upstream mobiledoc-kit library and the underlying problem is being tracked in multiple places on that repo, with the two most prominent issues being:

• Input on android and IME has a bug when typing first char bustle/mobiledoc-kit#589
• Entering logograms issues in macOS bustle/mobiledoc-kit#548

As such I'm going to close the issue here, any further discussion/PRs should be directed to the mobiledoc-kit project.

[xufangda]

This is an issue in the upstream mobiledoc-kit library and the underlying problem is being tracked in multiple places on that repo, with the two most prominent issues being:

• bustle/mobiledoc-kit#589
• bustle/mobiledoc-kit#548

As such I'm going to close the issue here, any further discussion/PRs should be directed to the mobiledoc-kit project.

As a blog platform, issues relating to the editor is a core issue. This is not something like a development or dependency issue. This issue occurs in every paragraph when user writes.

Can you imagine how annoying every time when you start a new paragraph, your first character jumps off?

It has been here for 2 years, and you don't resolve it, given the condition that one user has provided a solution after a long time suffering.

If you check out that user's blog, he has decided to leave ghost because of the attitude of the official team.

This issue has caused so much trouble for all Asian language speakers.

Very disappointed with the official team.

[kdyzm]

This is an issue in the upstream mobiledoc-kit library and the underlying problem is being tracked in multiple places on that repo, with the two most prominent issues being:

• bustle/mobiledoc-kit#589
• bustle/mobiledoc-kit#548

As such I'm going to close the issue here, any further discussion/PRs should be directed to the mobiledoc-kit project.

As a blog platform, issues relating to the editor is a core issue. This is not something like a development or dependency issue. This issue occurs in every paragraph when user writes.

Can you imagine how annoying every time when you start a new paragraph, your first character jumps off?

It has been here for 2 years, and you don't resolve it, given the condition that one user has provided a solution after a long time suffering.

If you check out that user's blog, he has decided to leave ghost because of the attitude of the official team.

This issue has caused so much trouble for all Asian language speakers.

Very disappointed with the official team.

In fact, what they want to say is that Asian users are not important, otherwise they would have solved the problem. After all, the users of this blogging platform are mainly Europeans and Americans. But I'm surprised that this bug has been resolved by some people, why don't they merge to master

[wuliaopage]

This issue has been closed, and no one will care about it.

For anyone who wants to push this bug to be fixed, Please show your support under the new open issue #11460.