Autocorrect with external keyboard on Samsung devices inserts duplicate characters on space

[gn-siva-k]

Description

When using an external keyboard on Samsung Android devices, triggering autocorrect by pressing Space after typing a partial word causes all characters of the word except the last one to be inserted into the editor — instead of autocorrecting/completing the word. This behavior is reproducible on the official Plate.js playground at platejs.org.

Reproduction URL

No response

Reproduction steps

1. Open https://platejs.org (or any Plate.js editor instance)
2. Connect an external keyboard to a Samsung Android device and use Samsung Browser
3. Start typing a word — e.g., type "hel" (intentional typo)
4. Press Space before finishing or correcting the word

Observe that instead of autocorrecting, the editor inserts something like "helhe" — all characters except the last one — followed by a space

Plate version

49.2.12

Slate React version

0.117.4

Screenshots

Logs

Browsers

Chrome

[zbeyens]

Does it happen in https://www.slatejs.org/#/rich-text ?

[JiwaniZakir]

This looks like a race condition between Samsung Browser's autocorrect composition events and Slate's input handling. When Space is pressed after a partially typed word, Samsung triggers an insertReplacementText (or deleteCompositionText + insertCompositionText) beforeinput sequence — but if Slate processes the raw keyboard input and the composition replacement independently, the already-typed characters get re-inserted on top of the corrected text, producing the "helhe" duplication pattern. The relevant handling is likely in withAndroid.tsx or the useAndroidInputManager hook, where Slate reconciles composition events with the DOM — Samsung's external keyboard path may not be setting isComposing correctly on the KeyboardEvent, causing the composition-aware code path to be bypassed entirely and falling back to naive character insertion alongside the autocorrect mutation.