Korean(Hangul) typing problem

[Comodoes]

Korean language bugs (when we type)

Thank you for the report. It’s generally better to post on issue per bug report. Do these bugs happen if you use source mode? Do these bugs happen here https://codemirror.net/try/?c=aW1wb3J0IHtiYXNpY1NldHVwLCBFZGl0b3JWaWV3fSBmcm9tICJjb2RlbWlycm9yIgppbXBvcnQge21hcmtkb3dufSBmcm9tICJAY29kZW1pcnJvci9sYW5nLW1hcmtkb3duIgppbXBvcnQge2xhbmd1YWdlc30gZnJvbSAiQGNvZGVtaXJyb3IvbGFuZ3VhZ2UtZGF0YSIKCi8vIFRoZSBNYXJrZG93biBwYXJzZXIgd2lsbCBkeW5hbWljYWxseSBsb2FkIHBhcnNlcnMKLy8gZm9yIGNvZGUgYmxvY2tzLCB1c2luZyBAY29k…

Unintentional Korean character added at the beginning of a note

This seems IME composition issue. Doubling OS and app(Obsidian) event. The problem is, isComposing: ture even after a key event. (e.g. enter, esc …) KeyboardEvent: isComposing property - Web APIs | MDN AFAIK many services solve this CJK IME problem by early returning if isComposing. I know nothing about React, but this is a case in React project: const handleKeyDown = (event: React.KeyboardEvent) => { if (event.nativeEvent.isComposing) return; ... };

Hopefully this bug will be fixed.