Skip to content
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

[Snyk] Upgrade axe-core from 4.10.0 to 4.10.2 #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

IT21336072
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade axe-core from 4.10.0 to 4.10.2.

ℹ️ 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 6 versions ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: axe-core
  • 4.10.2 - 2024-10-23

    This release prevents axe from sometimes crashing when a page changes in the middle of a test.

    Bug Fixes

    • get-ancestry: don't error when there is no parent (#4617) (6c07102)
  • 4.10.2-canary.d260ea8 - 2024-11-01
  • 4.10.2-canary.b7736de - 2024-11-11
  • 4.10.1 - 2024-10-16

    Because a few false positives were fixed, this release may see the number of reported issues go down. In pages with lots of very similar elements a performance bottleneck was fixed, allowing axe to finish sometimes up to 10x faster, although for most pages there won't be a difference. Lastly there is a small change to the ancestry selector of elements in shadow DOM. These weren't always guaranteed to be unique. The change means deduplication based on ancestry selectors may not work between 4.10.1 and older versions.

    Bug Fixes

  • 4.10.1-canary.7e9bacf - 2024-11-01
  • 4.10.1-canary.61dd5e3 - 2024-10-22
  • 4.10.0 - 2024-07-29

    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

    • new-rule: summary elements must have an accessible name (#4511) (0d8a99e), closes #4510

    Bug Fixes

    • aria-allowed-attr: allow aria-multiline=false for element with contenteditable (#4537) (f019068)
    • aria-allowed-attr: allow aria-required=false when normally not allowed (#4532) (2e242e1)
    • aria-prohibited-attr: allow aria-label/ledby on descendants of widget (#4541) (07c5d91)
    • aria-roledescription: keep disabled with { runOnly: 'wcag2a' } (#4526) (5b4cb9d), closes #4523
    • autocomplete-valid: incomplete for invalid but safe values (#4500) (e31a974), closes #4492
    • build: limit locales to valid files when using the --all-lang option (#4486) (d3db593), closes #4485
    • Prevent errors when loading axe in Angular + Jest (#4456) (3ef9353), closes #4400
    • Minor grammatical fixes for some rules and checks (#4499) (11fad59)
    • landmark-unique: follow spec, aside -> landmark (#4469) (e32f803), closes #4460
    • required-attr: allow aria-valuetext on slider instead of valuenow (#4518) (135898b), closes #4515
from axe-core GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade axe-core from 4.10.0 to 4.10.2.

See this package in npm:
axe-core

See this project in Snyk:
https://app.snyk.io/org/it21336072/project/b08f643f-c4dc-4e50-8e9f-0cbdd9cc7c05?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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants