-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8259687: JTabbedPane.setComponentAt doesn't hide previously visible tab component #9681
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
👋 Welcome back honkar! A progress list of the required criteria for merging this PR into |
@honkar-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. |
Webrevs
|
@@ -1598,6 +1598,11 @@ public void setComponentAt(int index, Component component) { | |||
boolean selectedPage = (getSelectedIndex() == index); | |||
|
|||
if (selectedPage) { | |||
if (this.visComp != null && | |||
!this.visComp.equals(component)) { | |||
// previous component visibility is set to false |
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.
It seems isVisible
is checked before changing the visibility..Should we do it here too?
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 thought it might be redundant since the setVisible() checks for visibility of component within show() and hide(). But to add clarity I have add isVisible
check.
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.
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 agree. The isVisible check is used for similar purposes so it's for the best to follow convention here and use it.
|
||
/* | ||
* @test | ||
* @bug 8265586 |
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.
bugid wrong
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.
Updated
@honkar-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 118 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) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
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.
Applied the change and ran your test. The test clearly shows the difference, and it looks good to me.
@@ -1598,6 +1598,11 @@ public void setComponentAt(int index, Component component) { | |||
boolean selectedPage = (getSelectedIndex() == index); | |||
|
|||
if (selectedPage) { | |||
if (this.visComp != null && | |||
!this.visComp.equals(component)) { | |||
// previous component visibility is set to false |
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 agree. The isVisible check is used for similar purposes so it's for the best to follow convention here and use it.
/integrate |
@honkar-jdk |
/sponsor |
Going to push as commit 891df21.
Your commit was automatically rebased without conflicts. |
@prsadhuk @honkar-jdk Pushed as commit 891df21. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
A simple change listener is used in JTabbedPane to lazily fill with components - this is done by adding the components to JTabbedPane using the
setComponentAt
in the change listener.Previously, if the change listener was placed before calling
addTab()
, the previous visible component was overlapping with the current visible component. To fix it, the visibility of previous component is set to false before the current component's visibility is set to true insetComponentAt
.Following are the before and after fix screenshots-
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9681/head:pull/9681
$ git checkout pull/9681
Update a local copy of the PR:
$ git checkout pull/9681
$ git pull https://git.openjdk.org/jdk pull/9681/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9681
View PR using the GUI difftool:
$ git pr show -t 9681
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9681.diff