[BUG] Character Disassembly Issue with Korean Input Bug in Collaborative Mode

[ctxwing]

Bug Description

I encountered a character disassembly issue in Appflowy main editro.
when typing the Korean word "한글입력". The typed result is garbled as "력 력려 려입ㄹㄹ 입입 입이 이글ㅇㅇ 글글 글그 ㄱ그한".
in window 10 and window 11. in MacOS BigSur it was ok ..

as you can see in the captured screen , when i typed in document name it was fine.
but when typing in main body (i mean main context.. character disassembly issue happen.
tying in engish was ok .

Would please investigate and resolve this issue. Thank you in advance..

How to Reproduce

in Window 10 and window 11

Expected Behavior

when i typed korean word ""한글입력", want to be show as is ""한글입력"

Operating System

window10, window11

AppFlowy Version(s)

0.5.7

Screenshots

Additional Context

as mensioned in above: only when main body typing is issue. doc title is ok ...
thanks in advance..

[ctxwing]

add some more infomation:

this case seems happening in multi editting. I've set self-hosted Appflowy-cloud. when sharing or co-editing a page, this korean character input distangled. I've tested (window11) with my colleague in Window10 , it happened.

while i was editng the same page alone, it is not happened ( typing was OK).

so i guess, this happens when n multi or co-editting.
FYI .
thanks in advance.

[LucasXu0]

#5220 (comment)

@ctxwing Does it happen on Windows 10 if only one person is editing?

[ctxwing]

@LucasXu0
i test newly again with latest appflowy 0.5.8

• PC1 : Window 11, appflowy 0.5.8, default IME (Microsoft IME) ... result OK
• PC2: Window 11, appflowy 0.5.8, 1) default IME (Microsoft IME) + 2) Hancom IME.... result was not OK.
  so, remove 2)Hancom IME, then It became works.OK
• PC3: Window 10, appflowy 0.5.8, default IME (Microsoft IME) ... result NOK
  see attached image 1, 2 (IME related)..

I've tested in both, single user case , and group uses case.
and it seems that i've mis led the fact that it is related co-editing case. sorry for mis-leding.
it is not co-editing but rather it is IME related.

the one remain issue is the case PC3 above, that is Win10+default IME case..
thanks again and hope to the lasted isssue be sovled.