-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
fix(mac): delete correct number of characters from current context when processing BMP or SMP deletes #11086
Conversation
User Test ResultsTest specification and instructions
Test Artifacts
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, this makes sense to me and I think it all lines up. I wasn't sure I spotted tests with complex selection vs text replacement scenarios though?
Which scenarios are you referring to? The focus of this PR is to fix #1643. I am hoping to not introduce any selection-related issues, but I have not attempted to research all selection scenarios and test those as part of this change. There is also an open issue #10093 that deals with that, though it specifies legacy apps in the description. |
I was going off this in the issue description:
|
Changes in this pull request will be available for download in Keyman version 17.0.299-beta |
When processing keystrokes for compliant apps (which have the ability to replace text while inserting characters from Keyman), the number of characters to delete must be determined correctly whether the context contains BMP code points or surrogate pairs. Also, if there is any text selected when the character is typed, the selection should also be replaced by the newly inserted character.
Fixes #1643
User Testing