iPadOS: Unable to type in Korean properly

[kimjihyo]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.97.1
• OS Version: iPadOS 18.2

Steps to Reproduce:

1. Open code-server or github codespace in mobile safari on iPad
2. Open a file (e.g. makrdown)
3. Type in Korean (e.g. ㄱ ㅏ)

Expected behavior: '가' should be typed in

Actual behavior: 'ㄱ가' is typed in

It was originally reported in https://github.com/microsoft/vscode/issues/114602 And it seems to be fixed with https://github.com/microsoft/vscode/issues/138095

It works as expected in vscode.dev, but the issue still happens in github codespace and code-server

[vs-code-engineering[bot]]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.97.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[aiday-mar]

Hi @kimjihyo thank you for filing this issue. May I ask you if you see this happening when the setting editor.experimentalEditContextEnabled is turned on when you are using codespaces or code-server?

[kimjihyo]

@aiday-mar Thanks for your reply! I couldn't find the editor.experimentalEditContextEnabled setting. I checked both settings.json and the settings UI, but it doesn't seem to exist. I tried it in the codespace with vscode version of 1.98.1, code-server with the version of 1.98.0, and vscode.dev with the version of 1.98.1.

I found that this Korean typing issue occurs in https://vscode.dev (1.98.1), whereas it worked as expected in the previous version. However, the issue doesn't occur in https://insiders.vscode.dev (1.99.0-insider).

Thanks for looking into this issue 😊

Edit: I was able to find editor.experimentalEditContextEnabled in https://vscode.dev on Windows using Chrome, but not on an iPad using Safari. It works perfectly fine on Windows though without the setting enabled.

[aiday-mar]

Hi thank you for the response. Yes so I forgot to mention that the setting is not yet available on the stable version of VS Code which is why you see it happening on https://vscode.dev/ but not on https://insiders.vscode.dev/, where the setting is turned on by default. Some time soon, we will enable this setting by default also on the stable version. In the meantime I invite you to use the nightly release, as you seem to say this issue is fixed on the nightly release with the setting turned on.

[kimjihyo]

Ok! Thank you for looking into this. I will close this issue.