-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8341978: Improve JButton/bug4490179.java #21474
8341978: Improve JButton/bug4490179.java #21474
Conversation
👋 Welcome back aivanov! A progress list of the required criteria for merging this PR into |
@aivanov-jdk 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 65 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@aivanov-jdk The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
/summary |
@aivanov-jdk Setting summary to:
|
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.
just some formatting comments, test is working fine for me on macos
|
||
private static volatile Point buttonCenter; | ||
|
||
private static final CountDownLatch windowGainedFocus = new CountDownLatch(1); |
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.
line here is too long and probably should be put in 2 lines
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.
I don't think it should, it's 86 column long, it nearly fits the 80-column limit; I don't think wrapping the line improves readability or clarity.
robot.waitForIdle(); | ||
|
||
if (actionPerformed.await(100, MILLISECONDS)) { | ||
throw new RuntimeException("Action event triggered by releasing button 3"); |
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.
line here also should be put into 2 lines
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.
I'm reluctant about changing it… The PR is approved now. And the line still fits 100-column limit.
Yet here it wrapping the line has its value, the button number is at the end of the line.
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.
I talked to @azvegint and we decided it's good enough. Wrapping the lines would require re-review.
/integrate |
Going to push as commit 8174cbd.
Your commit was automatically rebased without conflicts. |
@aivanov-jdk Pushed as commit 8174cbd. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
At first, I noticed bug4490179.java didn't release mouse button 1, which could affect the following tests.
I started looking at the test and updated it to use
CountDownLatch
instead of delays.@azvegint handled releasing mouse button 1 in #19339 (comment).
The updated version first verifies
mouseButton3Released
event is received and ensuresactionPerformed
is not received at this time.Then mouse button is released; this should trigger two events:
mouseButton1Released
andactionPerformed
. It is verified that these events are received.I kept debugging prints, they help understanding which actions lead to which events.
The updated test reproduces the original, it is easily verified using Java 8; the updated test is stable in CI.
The
javax/swing/JButton/bug4490179.java
test is also modified in #20861, @mrserb, could you take a look? I was going to suggested factoring out the changes to this test from #20861, yet I modified it myself. I realised it when I started creating the PR.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21474/head:pull/21474
$ git checkout pull/21474
Update a local copy of the PR:
$ git checkout pull/21474
$ git pull https://git.openjdk.org/jdk.git pull/21474/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21474
View PR using the GUI difftool:
$ git pr show -t 21474
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21474.diff
Webrev
Link to Webrev Comment