Skip to content
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

Try fix Korean IME on iOS #17680

Merged
merged 4 commits into from
Feb 1, 2025
Merged

Try fix Korean IME on iOS #17680

merged 4 commits into from
Feb 1, 2025

Conversation

kerams
Copy link
Contributor

@kerams kerams commented Dec 3, 2024

What does the pull request do?

Tries to fix #16956 on iOS.

What is the current behavior?

What is the updated/expected behavior with this PR?

See #16956

How was the solution implemented (if it's not obvious)?

With in a text box, when the user types , iOS invokes IUIKeyInput.DeleteBackward to remove , and then IUIKeyInput.InsertText with . Further typing should result in another delete followed by the insertion of .

However, the second IUIKeyInput.DeleteBackward does not currently happen and is inserted instead, producing 서ㄴ, probably due to how the previous delete was handled internally (resulting in the wrong return value from IUITextInput.TextInRange). With my change it is possible to type 3- and 4-character Korean syllabic blocks, but on only the first syllable. Additionally, manual deletion does not remove the entire syllable but only its last part ( becomes when deleting), which is the norm for Korean.

Sadly, further syllables continue to be broken, and manual deletes without calling keydown only select the final character. I'd appreciate any tips, especially describing why and how the double key up/down backspace invocation is required.

Checklist

Breaking changes

Obsoletions / Deprecations

@kerams kerams changed the title Try fix Korean IME on Android Try fix Korean IME on iOS Dec 3, 2024
@kerams
Copy link
Contributor Author

kerams commented Dec 12, 2024

Does Avalonia do any internal postprocessing of text entered in a TextBox? When I set the implementation of IUIKeyInput.DeleteBackward to be empty, I'd expect to see ㅅ서선 when typing , , , because IUIKeyInput.InsertText appends text, yet the text box correctly contains just despite disregarding the issued deletes.

I don't know how to explain this without the said postprocessing, and not sure I can fix the problem without understanding how this behavior is possible.

@kerams
Copy link
Contributor Author

kerams commented Jan 20, 2025

Nothing? It's quite embarrassing when a user reports to me that such a basic but crucial component as text input is not working properly...

I really want to get this fixed, but at this point I've spent hours of my time debugging the problem both on Android and iOS, so I could use some hints.

@cla-avalonia
Copy link
Collaborator

cla-avalonia commented Jan 20, 2025

  • All contributors have signed the CLA.

@Gillibald
Copy link
Contributor

"basic"

@kerams
Copy link
Contributor Author

kerams commented Jan 20, 2025

Is there someone else on the team besides this person that can help?

@Gillibald
Copy link
Contributor

Gillibald commented Jan 20, 2025

I have already given you plenty of information on the corresponding issue. IMEs communicate with the text view via: /~https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.Base/Input/TextInput/TextInputMethodClient.cs

Some IMEs require a special text store. We try to fulfill that requirement but it might not work as expected. First, try to understand how the iOS inputContext is working. Multiple protocols are involved. We might not implement some needed parts correctly. All you can do is to debug the order of events.

https://developer.apple.com/documentation/uikit/uitextinputdelegate?language=objc
https://developer.apple.com/documentation/uikit/uitextinput?language=objc

@kerams
Copy link
Contributor Author

kerams commented Jan 23, 2025

So it turns out the issue is very much akin to what's happening on Android. When iOS calls DeleteBackwards and InsertText to replace the last Korean syllabic block, SurroundingTextChanged ends up being raised, and the handler (which executes in the same context) feeds text change events back to iOS, supposedly messing with its keyboard/composition state. The solution is very adhoc, implemented based on AvaloniaInputConnection for Android - when we react to events from iOS that mutate text, we set a flag and then do nothing in SurroundingTextChanged. If you have a suggestion for a better solution, I want to hear it.

a.mp4

@kerams kerams marked this pull request as ready for review January 23, 2025 18:38
@avaloniaui-bot
Copy link

You can test this PR using the following package version. 11.3.999-cibuild0054522-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

@Gillibald Gillibald self-requested a review January 24, 2025 07:45
@avaloniaui-bot
Copy link

You can test this PR using the following package version. 11.3.999-cibuild0054659-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

Copy link
Contributor

@Gillibald Gillibald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Gillibald Gillibald added this pull request to the merge queue Feb 1, 2025
@Gillibald Gillibald added the backport-candidate-11.2.x Consider this PR for backporting to 11.2 branch label Feb 1, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 1, 2025
@timunie timunie added the bug label Feb 1, 2025
@timunie timunie added this pull request to the merge queue Feb 1, 2025
Merged via the queue into AvaloniaUI:master with commit 98e25c2 Feb 1, 2025
11 checks passed
@kerams kerams deleted the x branch February 1, 2025 12:44
@maxkatz6 maxkatz6 added backported-11.2.x and removed backport-candidate-11.2.x Consider this PR for backporting to 11.2 branch labels Feb 15, 2025
maxkatz6 pushed a commit that referenced this pull request Feb 15, 2025
* Do note propagate SurroundingTextChanged back to iOS

* Fix

* Optimize
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to type Korean 3-letter syllabic blocks
6 participants