Enabling autocorrect in MacOS with text replacements accepts replacements with any key press

[Monkatraz]

Describe the issue

If you use the Text Replacements feature in MacOS and enable autocorrect in the editor through an extension, typing a valid text to replace candidate has the suggested replacement apply on any key press, not just pressing space, enter or punctuation. It also doesn't seem to use the right cursor placement after the suggestion is accepted.

In this video, I have two text replacements, i -> I and omw -> On my way! (latter is stock in MacOS).

Screen.Recording.2025-06-25.at.4.58.15.PM.mov

What's supposed to happen is that if you type a valid candidate and you will get a tooltip for showing the replacement, and entering whitespace or punctuation after the word will automatically accept it. Typing anything else discards the replacement.

This has caused issues for some users on Replit - we use CodeMirror for one of our input boxes since we need things like decorations and change sets.

Browser and platform

MacOS, Chrome

Reproduction link

https://codemirror.net/try/#c=aW1wb3J0IHttaW5pbWFsU2V0dXAsIEVkaXRvclZpZXd9IGZyb20gImNvZGVtaXJyb3IiCgpjb25zdCBlbmFibGVBdXRvQ29ycmVjdCA9IEVkaXRvclZpZXcuY29udGVudEF0dHJpYnV0ZXMub2YoewogIGF1dG9jb3JyZWN0OiAnb24nCn0pCgpuZXcgRWRpdG9yVmlldyh7CiAgZG9jOiAiLi4uIiwKICBleHRlbnNpb25zOiBbCiAgICBtaW5pbWFsU2V0dXAsCiAgICBlbmFibGVBdXRvQ29ycmVjdCwKICBdLAogIHBhcmVudDogZG9jdW1lbnQuYm9keQp9KQo=

[marijnh]

This seems to be another bug in Chrome's EditContext implementation. The same issue can be seen on https://mdn.github.io/dom-examples/edit-context/html-editor/ . I've filed it as issue 428112177.

You can suppress the use of EditContext by setting EditorView.EDIT_CONTEXT = false.

[marijnh]

I've disabled EditContext on non-Android browsers (where we don't need it all that badly) in patch 6ea9dd610bec3a36, because Chrome's implementation just isn't very solid.

[Monkatraz]

I've disabled EditContext on non-Android browsers (where we don't need it all that badly) in patch 6ea9dd610bec3a36, because Chrome's implementation just isn't very solid.

Thanks! We'll upgrade our CodeMirror version. It's a shame that there are still issues with Chrome's implementation...