[Snyk] Upgrade axe-core from 4.3.3 to 4.10.0 #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade axe-core from 4.3.3 to 4.10.0. See this package in npm: axe-core See this project in Snyk: https://app.snyk.io/org/stanislav1975/project/18f3154f-26c5-4466-a94f-d97f7b9bb0b1?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade axe-core from 4.3.3 to 4.10.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 486 versions ahead of your current version.
The recommended version was released on 21 days ago.
Release notes
Package name: axe-core
This axe-core release introduces a new rule for testing the HTML summary element. Additionally, a number of false positives have been fixed. Upgrading to this release may therefore both increase, or decrease the number of issues found on a website. Most likely the impact of upgrading from axe-core 4.9.2 to axe-core 4.10.0 should be minimal.
Features
Bug Fixes
This release addresses a number of false positives, which may result in fewer issues reported. It also prevents a problem where axe-core wouldn't load on pages due to a conflict with a long-ago deprecated javascript library.
Bug Fixes
Features
Bug Fixes
overflow: hiddenancestor (#4357) (bdb7300), closes #4253This release should not result in different issue numbers. For TypeScript users, an error in type definitions has been corrected. This release could require a correction to how axe-core types are used. This release may change selectors on elements with the
xmlnsattribute, as the selectors axe-core prosed with those was invalid. Deduplication based on selectors between this and and prior versions of axe-core can fail because of this change.Bug Fixes
This release will not change axe-core's results. Only needed when used with old versions of NodeJS.
Bug Fixes
Bug Fixes
This release does not change the number of issues reported.
Bug Fixes
This axe-core release makes various changes to impact. As a result issues previously reported in one rule may now be reported under a different rule. In rarer cases, the impact under which an issue is reported may change. This release has further deprecated the
duplicate-idandduplicate-id-activerule, along with setting theduplicate-id-ariato always report as "needs review" rather than as a violation. As these three rules are fairly common causes of issues, this change may result in the total issue reported going down significantly.Consistent Rule Impact
This release changes it so that a rule never changes what impact it reports. To facilitate this while without changing the impact on certain issues, some rules have been split. The following changes were involved:
Other Features
Type Fixes & Improvements
Various improvements were made to the types. Potentially the most impactful of which is that the
targetandancestryproperty now return asUnlabelledFrameSelectorinstead of asstring[], which is incorrect for selectors involving shadow DOM. This may create some issues during migration for any code that has been incorrectly assuming these two properties have thestring[]type. For more details and other type changes, see the commit itself:Bug Fixes
This release corrects the Trusted Tester v5 tags, which were introduced in 4.7.0, and it addresses a few false positives which for pages with forms may result in a few less issues found.
Bug Fixes
This release addresses a number of bugs. Some things that were failed in the previous release may now be passed or require manual review.
Bug Fixes