-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8268284: javax/swing/JComponent/7154030/bug7154030.java fails with "Exception: Failed to hide opaque button" #4792
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
Conversation
…xception: Failed to hide opaque button" Reducing the height of the analyzed area to get rid of the rounded edges at the botom of the frame. Apparently shadow outside of it being rendered by Mac OS X Big Sur inconsistently which gives random test failures on M1 macs with Big Sur.
|
👋 Welcome back kizune! A progress list of the required criteria for merging this PR into |
|
@azuev-java 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. |
Webrevs
|
| locy = bounds.y + insets.top; | ||
| frw = bounds.width - insets.left - insets.right; | ||
| frh = bounds.height - insets.top - insets.bottom; | ||
| frh = bounds.height - insets.top - insets.bottom - 25; |
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.
Will making frame undecorated help instead of this?
Can you also please give a CI job running this test on all platforms for several iterations?
Since this test has undergone multiple iterations, can you please confirm that this test still fails without 7154030 fix?
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.
Will making frame undecorated help instead of this?
Yes, seems like making it undecorated fixes the issue. I can not provide many failure results since failures were pretty uncommon in the first place. As for the test run i will add link to it into the bug comment.
|
I also suggest to apply some suggestions from here: |
As i pointed before - after frame is visible taking its coordinates from main thread should not be a problem - in all the cases so far i never had a case where coordinates were miscalculated. But if it makes you happy - it is no harm in moving of this functionality to invokeAndWait block. Here. |
It is a problem since these coordinates and other states of the swing components are accessed without any synchronization on the main thread, this can lead to incorrect values being read, it is safe and good to always access Swing on EDT only. |
mrserb
left a comment
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.
Looks fine
|
@azuev-java 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 78 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 |
|
/integrate |
|
Going to push as commit 534f005.
Your commit was automatically rebased without conflicts. |
|
@azuev-java Pushed as commit 534f005. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Reducing the height of the analyzed area to get rid of the rounded edges
at the botom of the frame. Apparently shadow outside of it being
rendered by Mac OS X Big Sur inconsistently which gives random test
failures on M1 macs with Big Sur.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4792/head:pull/4792$ git checkout pull/4792Update a local copy of the PR:
$ git checkout pull/4792$ git pull https://git.openjdk.java.net/jdk pull/4792/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4792View PR using the GUI difftool:
$ git pr show -t 4792Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4792.diff