-
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
JDK-8311893: Interactive component with ARIA role 'tabpanel' does not have a programmatically associated name #16148
Conversation
👋 Welcome back psoujany! A progress list of the required criteria for merging this PR into |
Webrevs
|
@RealCLanger Could you please review my changes. Thank you. |
Sorry, that's not my turf. Somebody from javadoc area should pick this up. However, could you please enable Github Actions testing for your repo? Thanks. |
@jonathan-gibbons Could you please review my changes. Thank you. |
@psoujany 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! |
Can anyone review this PR. |
@psoujany 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! |
Can anyone review this PR. Thanks. |
@hns ? |
Thank you for your contribution. As a general rule, whenever a change like this is made, we provide or update a regression test, to verify the fix works as expected, and to ensure that it stays fixed. If there are reasons why it is not necessary to write a test, you should put a suitable |
Thank you @jonathan-gibbons. I'll check on the regression tests. |
I do agree that the Looking at this example as a blueprint, I think the solution should be the following:
Note: I have up updated this comment as I initially misunderstood the diff and how it related to generated HTML. |
There are quite a few tests failing because of this change, which need to be updated once we agree on the proper solution. |
@hns Thanks for your review. Will look into the changes. |
@psoujany some of the additional changes such as updating |
@hns As this PR addresses below comment. I want this PR to be contributed with the below proposal. Others you can handle. Please let me know if this is fine with you. I'll update code and testcases involved with this change as well. Thank you. |
@psoujany just to make sure we're on the same page, you'll also update the tests required by this change? |
Hi @hns , yes I'm trying to run jtreg testcases with this code changes. I would like to fix the testcase as well, I'll reach out to you for help in case of any queries. Thank you. |
@hns I've modified regression tests with the code changes and see langtools jtreg tests passing with the new fixes. Could you please review this PR. Thank you. |
@psoujany I still get two failing tests, possibly because I updated my local repository by merging the current master branch before running tests. This PR is based on a very outdated branch, so we should definitely merge the master branch before integrating. The failing tests I get on my up-to-date branch are these: jdk/javadoc/doclet/testPreview/TestPreview.java |
@hns I've updated my branch and modified the failing tests. Now all tests seems passing with the changes. Thank you. |
Thanks @psoujany, this looks good now. Although |
@psoujany the last thing that needs to be updated is to change |
@hns Thank you for the help. I've updated your suggested change 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.
Thanks for fixing the tests, @psoujany! This looks good now.
@psoujany 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 31 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 (@hns) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@hns Could you please sponsor this PR. Thank you. |
/sponsor |
Going to push as commit 783ae56.
Your commit was automatically rebased without conflicts. |
Interactive component with ARIA role 'tabpanel' does not have a programmatically associated name in javadoc which is failing Accessibility checks.
https://bugs.openjdk.org/browse/JDK-8311893
https://bugs.openjdk.org/browse/JDK-8311894
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16148/head:pull/16148
$ git checkout pull/16148
Update a local copy of the PR:
$ git checkout pull/16148
$ git pull https://git.openjdk.org/jdk.git pull/16148/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16148
View PR using the GUI difftool:
$ git pr show -t 16148
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16148.diff
Webrev
Link to Webrev Comment