Skip to content

fix(chat): properly handle Korean IME input in message textarea #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

keenranger
Copy link

This PR fixes an issue where pressing Enter while typing in Korean using an IME caused duplicate input or premature message submission.

Changes

  • Added onCompositionStart and onCompositionEnd to track IME composition.
  • Ensured Enter does not trigger message submission while composing characters.

Testing

  • Verified correct handling of Korean IME input.
  • Confirmed expected behavior for Enter and Shift+Enter.

Before Fix

The screenshot below shows the issue where messages were being duplicated:
스크린샷 2025-02-03 오후 7 19 18

- Added `onCompositionStart` and `onCompositionEnd` handlers to track IME composition.
- Prevented premature message submission by ensuring `onKeyDown` does not trigger while composing.
- This fixes an issue where pressing Enter while typing Korean caused duplicate input.

Signed-off-by: Hankyeol Kyung <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant