On Sat, 25 May 2024 23:16:02 GMT, Phil Race <p...@openjdk.org> wrote:
>>> I'm able to build this again, but not satisfied that it solves the issue, >>> so I am still investigating. Should I rebase this upon latest master or >>> somewhere else (now that 22 is released)? @prrace >> >> @srl295 >> You are based on main-line, which is now 23, so there should be nothing to >> do. >> If you feel you are out of date in some important way you can re-base but >> the release change would have nothing to do with that. > >> @prrace any hope of backporting this? I can do it if you point me at the >> steps > > @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 > and the list of update releases and any specific policies they may have are > here > https://openjdk.org/projects/jdk-updates/ > > > But yes, you should be able to do it. The census indicate you have the needed > status. @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 `javafx.scene.control.TextField` - should that be affected (that is, fixed) by this fix to AWTView or would JFX be perhaps similar parallel code needing a parallel fix? ------------- PR Comment: https://git.openjdk.org/jdk/pull/17921#issuecomment-2462924184
