Issue with Hangul Input Closing MentionCombobox Unexpectedly

[SID9-HoneyBee]

Hello Plate.js Team,

I am experiencing an issue with the MentionCombobox component in Plate.js where the combobox closes unexpectedly when typing in Hangul (Korean script). Below are the details:

Description:

• When I start typing Hangul characters using the combobox triggered by '@', the combobox closes as soon as I start typing. This behavior interrupts the input process and prevents selecting any mentions.

Steps to Reproduce:

1. Configure a MentionCombobox with a trigger character '@'.
2. Begin typing in Hangul within the combobox.
3. Notice that the combobox closes immediately upon input.

Expected Behavior:
The combobox should remain open, allowing for the completion of Hangul character input and subsequent selection of mentions from the list.

Possible Issue Areas:

• I suspect this might be related to how key events are handled during IME composition of Hangul characters, where intermediate states might be causing the combobox to lose focus or prematurely determine input completion.

Environment:

• Plate.js version: [30.1.2]

I appreciate any guidance or fixes you could provide on this issue, as it is impacting the usability for Korean users significantly.

Thank you!

[zbeyens]

Does it happen in https://plate-ph6jqyzgg-udecode.vercel.app/?

[SID9-HoneyBee]

For some reason, neither the Playground nor the Mention Element examples are working after the trigger is activated (could it be an issue with my browser environment?). Although the MentionCombobox is activated, no search occurs, but it does not close unexpectedly. Additionally, since all the linked data is in English, it is difficult to verify whether the search function properly supports Hangul (Korean script).

[zbeyens]

This preview comes from this rework #3168

You could try to fork the branch to test korean items

[SID9-HoneyBee]

thank you After forking the branch, we will conduct a test together.

[SID9-HoneyBee]

This was definitely not a bug, it was simply an issue with the slate version.
At the time of my testing, the versions of slate and slate-react were 0.101.5 and 0.101.6, respectively, and the problem was resolved after updating both to 1.102.0.