-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8195675: Call to insertText with single character from custom Input Method ignored #17921
Conversation
👋 Welcome back srl! A progress list of the required criteria for merging this PR into |
- externalize "keyman"
Webrevs
|
@@ -965,7 +968,7 @@ - (void) insertText:(id)aString replacementRange:(NSRange)replacementRange | |||
|
|||
if ((utf16Length > 2) || | |||
((utf8Length > 1) && [self isCodePointInUnicodeBlockNeedingIMEvent:codePoint]) || | |||
((codePoint == 0x5c) && ([(NSString *)kbdLayout containsString:@"Kotoeri"]))) { | |||
[(NSString *)kbdLayout containsString:@KEYMAN_LAYOUT]) { | |||
#ifdef IM_DEBUG |
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.
As noted in JBS Kotoeri is obsolete, which is why the reference to it here should be removed as part of this change.
@srl295 This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
I'm able to build this again, but not satisfied that it solves the issue, so I am still investigating. |
@srl295 |
Great. I'll keep investigating |
@srl295 This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Just got my Mac setup again today - will commence testing |
@prrace i want to verify it fixes the issue. |
@prrace any hope of backporting this? I can do it if you point me at the steps |
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.
@srl295
You just need to add a comment saying
/integrate
I can't do that for you.
Since you are a JDK committer, it will then be pushed
@SRL - that's not my call. The update release maintainers are in charge The general process is https://openjdk.org/projects/jdk-updates/approval.html But yes, you should be able to do it. The census indicate you have the needed status. |
Thanks. I think I might not try it on the weekend before a US holiday :) But i'll do it Tuesday |
/integrate |
Going to push as commit b8f2ec9.
Your commit was automatically rebased without conflicts. |
@prrace hi- opened a backport as openjdk/jdk21u-dev#1052 with a backport JBS |
/backport 17u |
@srl295 The target repository |
/backport openjdk/jdk17u |
/backport openjdk/jdk11u-dev |
@srl295 Could not automatically backport
Please fetch the appropriate branch/commit and manually resolve these conflicts by using the following commands in your personal fork of openjdk/jdk17u. Note: these commands are just some suggestions and you can use other equivalent commands you know.
Once you have resolved the conflicts as explained above continue with creating a pull request towards the openjdk/jdk17u with the title Below you can find a suggestion for the pull request body:
|
@srl295 Could not automatically backport
Please fetch the appropriate branch/commit and manually resolve these conflicts by using the following commands in your personal fork of openjdk/jdk11u-dev. Note: these commands are just some suggestions and you can use other equivalent commands you know.
Once you have resolved the conflicts as explained above continue with creating a pull request towards the openjdk/jdk11u-dev with the title Below you can find a suggestion for the pull request body:
|
@srl295 Could not automatically backport
Please fetch the appropriate branch/commit and manually resolve these conflicts by using the following commands in your personal fork of openjdk/jdk8u-dev. Note: these commands are just some suggestions and you can use other equivalent commands you know.
Once you have resolved the conflicts as explained above continue with creating a pull request towards the openjdk/jdk8u-dev with the title Below you can find a suggestion for the pull request body:
|
@prrace the backports seem to be progressing well.. there's a report that it's not working with JavaFX, though. I'm not familiar with JFX enough to know about this. Do you think there's either a special backport needed, or could there be a parallel fix in JFX that's needed? @AndyBlack created https://github.com/AndyBlack/KeymanFX and https://github.com/AndyBlack/KeymanSwing as test cases. It seems that on the JFX side it's using |
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17921/head:pull/17921
$ git checkout pull/17921
Update a local copy of the PR:
$ git checkout pull/17921
$ git pull https://git.openjdk.org/jdk.git pull/17921/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17921
View PR using the GUI difftool:
$ git pr show -t 17921
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17921.diff
Webrev
Link to Webrev Comment