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
8287912: GTK L&F : Background of tree icons are red #10112
Conversation
👋 Welcome back kumarabhi006! A progress list of the required criteria for merging this PR into |
@kumarabhi006 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
|
@@ -0,0 +1,112 @@ | |||
|
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.
remove this empty line
|
||
if (c.equals(Color.RED)) { | ||
passed = true; | ||
} |
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.
better to check at midpoint tree.width/2, tree.height/2 and also break if it's RED, no need to check all pixels.
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.
Another possible solution that I used in a previous test was a midpoint as suggested, but also one pixel near each edge. This eliminates the chance of the red still existing but not being detected at the midpoint because the red is at a different location.
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.
The test check has been changed to compare the pixels of entire width keeping the height constant to half of tree height. Now it will check pixel color and if it is not red , the test will fail.
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.
For me, test is not failing without the fix.
Also, if you test entire width and fail if it is not red, it might encounter black pixel of text font too and might fail, so I think it's better to check width/2 to width -1 and not entire width.
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.
Also, it's might be better to write the image in case of failure so that it gives an idea why it failed.
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.
For me, test is not failing without the fix. Also, if you test entire width and fail if it is not red, it might encounter black pixel of text font too and might fail, so I think it's better to check width/2 to width -1 and not entire width.
Test was not failing without the fix because the second argument of getRGB method is height/2, and for that pixel value the returned color is red.
Changing the argument from height/2 to height/4 will fail the test without the fix otherwise it will pass the test.
Also writing the image in case of failure.
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 ok .Please remove the empty 1st line in the test.
} | ||
} | ||
} | ||
if (!passed) { |
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 test will pass even in the case of last pixel check is RED. We should check for pixel data and whenever it is not RED we should bail out.
Also if test fails it will leave TreeBackgroundColorTestFail.png, we should use temporary file and delete it on exit.
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 have removed the writing of test image in case of fail operation and test condition changed to check if pixel color is not red then test will fail.
@kumarabhi006 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 751 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. 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 (@prsadhuk, @jayathirthrao) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@kumarabhi006 |
/sponsor |
Going to push as commit a92c1ff.
Your commit was automatically rebased without conflicts. |
@jayathirthrao @kumarabhi006 Pushed as commit a92c1ff. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The background of tree icons are not red in GTK LAF when setOpaque is set to false for tree component.
It has been observed that while painting tree cell background in GTK LAF, a rectangular area is also painted with background color (white).
Proposed solution is to check the opacity of tree component before drawing tree cell background. If the opacity is set to "false" then the background shouldn't be painted.
An automated test case has been added and checked in CI, link is added in JBS.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10112/head:pull/10112
$ git checkout pull/10112
Update a local copy of the PR:
$ git checkout pull/10112
$ git pull https://git.openjdk.org/jdk pull/10112/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10112
View PR using the GUI difftool:
$ git pr show -t 10112
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10112.diff