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
8242544: CMD+ENTER key event crashes the application when invoked on dialog #714
Conversation
|
Webrevs
|
Note: This PR proposes an alternative fix to the one put forth in #704. This fix is simpler and less intrusive. /reviewers 2 |
@kevinrushforth |
The fix looks good, and as mentioned above, is minimally intrusive. I also ran a full set of tests with no problems. It would be helpful to add a manual test as part of this PR (maybe based on the test from the bug report). |
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.
This looks good with the current tools/OS behaviour. It is still a bit of a hack, which may result in unexpected behaviour when the macos-specific tools change.
But this is a general observation with macos, so I believe this is indeed the best (and least intrusive way) to prevent the crashes.
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.
This PR fixes the JDK-8242544 issue as intended. I've added a couple of minor comments.
Regarding #704, which also fixed the related issue JDK-8205915 but was targeting JDK-8242544, maybe it should be just updated to target the former?
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.
In the interest of getting as much testing as possible, I'm approving this fix now. If there isn't time to add a manual test, then it can be done in the jfx18
branch during RDP1.
@beldenfox This change now passes all automated pre-integration checks. 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 As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@johanvos, @jperedadnr, @kevinrushforth) but any other Committer may sponsor as well.
|
The manual test for this can also cover JDK-8205915 (a Cmd-based shortcut can be processed by two separate windows). This crash was blocking testing on that bug. I'll submit a fix for JDK-8205915 along with the manual test tomorrow. |
/integrate |
@beldenfox |
/sponsor |
Going to push as commit a2a0acf. |
@kevinrushforth @beldenfox Pushed as commit a2a0acf. |
The OS crashes if the contentView of a window is set to nil while handling processKeyEquivalent. With this PR we just set the contentView to a basic do-nothing NSView for the interim.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jfx pull/714/head:pull/714
$ git checkout pull/714
Update a local copy of the PR:
$ git checkout pull/714
$ git pull https://git.openjdk.java.net/jfx pull/714/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 714
View PR using the GUI difftool:
$ git pr show -t 714
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jfx/pull/714.diff