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

chore(deps): bump tabbable from 4.0.0 to 6.0.0 #72

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

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Aug 26, 2022

Bumps tabbable from 4.0.0 to 6.0.0.

Release notes

Sourced from tabbable's releases.

v6.0.0

Major Changes

  • 5f40c8e: Revised and clarified official browser support (still as broad and deep as reasonably possible).
  • 5f40c8e: 🚨 Breaking: Dropped support of IE browsers, all versions.
    • IE11 was officially retired on June 15, 2022 (6 weeks ago). There are no longer any versions of IE that are still maintained or even supported by Microsoft.
  • a09ba0b: 🚨 Breaking: Default displayCheck 'full' option no longer treats detached nodes as visible. Use the new 'legacy-full' option to restore old (incorrect) behavior only if you must. Ideally, make sure tabbable only runs once all nodes of interest have been attached to the document.

v5.3.3

Patch Changes

  • 0210a1c: fix: align with browser behaviour when a web component has a negative tabindex

v5.3.2

Patch Changes

  • 320bfd1: Updated docs for displayCheck configuration.
  • aa2a699: Fixed an issue with displayCheck=full (default setting) determining all nodes were hidden when the container is not attached to the document. In this case, tabbable will revert to a displayCheck=none mode, which is the equivalent legacy behavior. Also updated the displayCheck option docs to add warnings about this corner case for the full and non-zero-area modes. non-zero-area behaves differently in the corner case. See the docs for more info.

v5.3.1

Patch Changes

  • cf1da66: Add warnings and help in documentation about running tabbable under JSDom (e.g. with Jest). JSDom is not technically supported, and 5.3.0 introduced some changes that use DOM APIs that JSDom stubs out, which may cause some JSDom-based tests to fail. Also revamp the API docs a bit to make them clearer, and add missing getShadowRoot option to isTabbable() and isFocusable() (docs only; no code changes necessary).

v5.3.0

Minor Changes

  • 685a906: Adds new Shadow DOM support (must be explicitly enabled using the new getShadowRoot option).
    • When enabled, supports open shadows by default, and can support closed shadows if the option is a function that returns the shadow for a given node. See documentation for more information.
    • Includes all updates from 5.3.0-beta.0 and 5.3.0-beta.1 releases.

Patch Changes

  • b341412: Made "isDisabledFromFieldset" more readable and concise (even marginally faster).
  • 685a906: Fixed a bug in getTabIndex: the tab index of <audio>, <video> and <details> was left to the browser default if explicitly set to a value that couldn't be parsed as integer, leading to inconsistent behavior across browsers. Also slightly modified the function's logic to make it more efficient. Finally added tests to cover the fix.
  • dd6d0ec: Optimized and extended displayCheck: "full" option (now checks for any element having no display boxes) and added test for display: "contents" property (this bug was never reported). [(#592)](focus-trap/tabbable#592)
  • 193fca2: Fixed bug in isDisabledFromFieldset. The function wasn't checking whether the disabled <fieldset> containing node is the top-most disabled <fieldset> (#596).

v5.2.1

Patch Changes

  • 1d5fcb5: Fixed: Form elements in disabled fieldsets should not be tabbable/focusable (#413)

v5.2.0

Minor Changes

  • bf0a8f0: Exposed an option to select the way that an element is checked as displayed

v5.1.6

Patch Changes

... (truncated)

Changelog

Sourced from tabbable's changelog.

6.0.0

Major Changes

  • 5f40c8e: Revised and clarified official browser support (still as broad and deep as reasonably possible).
  • 5f40c8e: 🚨 Breaking: Dropped support of IE browsers, all versions.
    • IE11 was officially retired on June 15, 2022 (6 weeks ago). There are no longer any versions of IE that are still maintained or even supported by Microsoft.
  • a09ba0b: 🚨 Breaking: Default displayCheck 'full' option no longer treats detached nodes as visible. Use the new 'legacy-full' option to restore old (incorrect) behavior only if you must. Ideally, make sure tabbable only runs once all nodes of interest have been attached to the document.

5.3.3

Patch Changes

  • 0210a1c: fix: align with browser behaviour when a web component has a negative tabindex

5.3.2

Patch Changes

  • 320bfd1: Updated docs for displayCheck configuration.
  • aa2a699: Fixed an issue with displayCheck=full (default setting) determining all nodes were hidden when the container is not attached to the document. In this case, tabbable will revert to a displayCheck=none mode, which is the equivalent legacy behavior. Also updated the displayCheck option docs to add warnings about this corner case for the full and non-zero-area modes. non-zero-area behaves differently in the corner case. See the docs for more info.

5.3.1

Patch Changes

  • cf1da66: Add warnings and help in documentation about running tabbable under JSDom (e.g. with Jest). JSDom is not technically supported, and 5.3.0 introduced some changes that use DOM APIs that JSDom stubs out, which may cause some JSDom-based tests to fail. Also revamp the API docs a bit to make them clearer, and add missing getShadowRoot option to isTabbable() and isFocusable() (docs only; no code changes necessary).

5.3.0

Minor Changes

  • 685a906: Adds new Shadow DOM support (must be explicitly enabled using the new getShadowRoot option).
    • When enabled, supports open shadows by default, and can support closed shadows if the option is a function that returns the shadow for a given node. See documentation for more information.
    • Includes all updates from 5.3.0-beta.0 and 5.3.0-beta.1 releases.

Patch Changes

  • b341412: Made "isDisabledFromFieldset" more readable and concise (even marginally faster).
  • 685a906: Fixed a bug in getTabIndex: the tab index of <audio>, <video> and <details> was left to the browser default if explicitly set to a value that couldn't be parsed as integer, leading to inconsistent behavior across browsers. Also slightly modified the function's logic to make it more efficient. Finally added tests to cover the fix.
  • dd6d0ec: Optimized and extended displayCheck: "full" option (now checks for any element having no display boxes) and added test for display: "contents" property (this bug was never reported). [(#592)](focus-trap/tabbable#592)
    • ⚠️ This will likely break your tests if you're using JSDom (e.g. with Jest). See testing in JSDom for more info.
  • 193fca2: Fixed bug in isDisabledFromFieldset. The function wasn't checking whether the disabled <fieldset> containing node is the top-most disabled <fieldset> (#596).

5.3.0-beta.1

  • Add support for setting getShadowRoot: true as an easy way to simply enable shadow DOM support. This is the equivalent of setting getShadowRoot: () => false, which means tabbable will find nodes in open shadow roots only.

5.3.0-beta.0

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by stefcameron, a new releaser for tabbable since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Aug 26, 2022
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/tabbable-6.0.0 branch from 6eec019 to 6bf0e47 Compare September 9, 2022 14:03
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/tabbable-6.0.0 branch from 6bf0e47 to 96a2e8a Compare October 13, 2022 19:11
Bumps [tabbable](https://github.com/focus-trap/tabbable) from 4.0.0 to 6.0.0.
- [Release notes](https://github.com/focus-trap/tabbable/releases)
- [Changelog](https://github.com/focus-trap/tabbable/blob/master/CHANGELOG.md)
- [Commits](focus-trap/tabbable@4.0.0...v6.0.0)

---
updated-dependencies:
- dependency-name: tabbable
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/tabbable-6.0.0 branch from 96a2e8a to 347f42a Compare November 4, 2022 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants