8154043: Fields not reachable anymore by tab-key, because of new tabbing behaviour of radio button groups.

[ktakakuri]

This is a backport of JDK-8154043: Fields not reachable anymore by tab-key, because of new tabbing behaviour of radio button groups.

Applying the JDK-8154043 fix as is will result in a regression of JDK-8182577.
The fix of JDK-8182577 adds an interface for JDK10, therefore this fix cannot be backported simply for JDK8u.
So, I propose to judge the buttonModel is an instance of DefaultButtonModel.

Testing:
java/awt
javax/swing
ButtonGroupLayoutTraversalTest.java
bug8033699.java
DefaultButtonModelCrashTest.java
on Windows x86_64

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• JDK-8154043 needs maintainer approval
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8182577 needs maintainer approval
• Change requires a CSR request matching fixVersion openjdk8u452 to be approved (needs to be created)

Issues

• JDK-8154043: Fields not reachable anymore by tab-key, because of new tabbing behaviour of radio button groups. (Bug - P3 - Rejected)
• JDK-8182577: Exception when Tab key moves focus to a JCheckbox with a custom ButtonModel (Bug - P3)

Reviewers

• Paul Hohensee (@phohensee - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/285/head:pull/285
$ git checkout pull/285

Update a local copy of the PR:
$ git checkout pull/285
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/285/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 285

View PR using the GUI difftool:
$ git pr show -t 285

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/285.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back ktakakuri! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[ktakakuri]

Could someone please review this backport?

[ktakakuri]

@mrserb
I issued this PR in relation to #212.
Could you please review this backport?

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[ktakakuri]

Could someone please review this backport?

[mlbridge]

Webrevs

• 02: Full - Incremental (a1eac9d6)
• 01: Full - Incremental (cc8ef7ee)
• 00: Full (6a8e5fe6)

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[phohensee]

Copyright date updates should be taken from the original commit rather than use the current year. If the existing file has a later copyright date than the file in the original commit, leave the copyright date alone. Other than that, lgtm.

[mrserb]

Sorry I did not have a time to look at this PR, will try to look soon.

[ktakakuri]

I corrected the copyright date.

[openjdk]

@ktakakuri This change is no longer ready for integration - check the PR body for details.

[openjdk]

⚠️ @ktakakuri This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[jerboaa]

As this fix includes the test from JDK-8182577, please use /isssue add JDK-8182577.

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.

[ktakakuri]

/open

[openjdk]

@ktakakuri This pull request is now open

[ktakakuri]

/isssue add JDK-8182577

[openjdk]

@ktakakuri Unknown command isssue - for a list of valid commands use /help.

[jerboaa]

My bad /issue add JDK-8182577

[ktakakuri]

/issue add JDK-8182577

[openjdk]

@ktakakuri
Adding additional issue to issue list: 8182577: Exception when Tab key moves focus to a JCheckbox with a custom ButtonModel.

[openjdk]

At least one of the issues associated with this backport has a resolved CSR for a different version. As this means that this backport may also need a CSR, the csr label is being added to this pull request to signal this potential requirement. The command /csr unneeded can be used to remove the label in case a CSR is not needed.

[ktakakuri]

@phohensee
Is it OK to request a fix request?

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[ktakakuri]

@theRealAph
What is the reason for fix-no?
What should I do next?

[ktakakuri]

What is the status of this backport now?

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[phohensee]

I filed a backport JBS issue JDK-8337619, and an associated backport CSR JDK-8337620. Follow the standard CSR process to get it reviewed and approved. It may not be approved, since it add a public method to an existing API, which afaik can't be done without an update JSR.

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[ktakakuri]

Is there anything I should do now?
Should I just wait for a review?

[phohensee]

You need a backport CSR approved for https://bugs.openjdk.org/browse/JDK-8182577. The backport CSR https://bugs.openjdk.org/browse/JDK-8337619 is linked from the backport JBS issue https://bugs.openjdk.org/browse/JDK-8337619.

[ktakakuri]

Unlike jdk10, this backport does not add any interfaces.
Is it still necessary for the CSR to be approved?

[theRealAph]

Unlike jdk10, this backport does not add any interfaces. Is it still necessary for the CSR to be approved?

I don't think so. But there are some complex issues with the jdk 8 backport described in the comments to https://bugs.openjdk.org/browse/JDK-8154043 , which I think is why the 8 bakport was denied in 2016. What I do not understand is why, when the backport was denied 8 years ago, it should be allowed today. If someone can explain that, we can have a meningful discussion.

[ktakakuri]

Why was the jdk8 backport denied in 2016?
I tried to find it through JBS and email but could not find it.
If adding an interface is the problem, this backport is fine.

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[ktakakuri]

@theRealAph If you have any information, I would appreciate it if you could share it with me.

[bridgekeeper]

@ktakakuri This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[ktakakuri]

I comment to not close.