focus-trap-react - npm Package Versions

8.7.0

Minor Changes

• 7fbe8ca: Update to support new features in focus-trap@6.6.0 including initialFocus which can now be false to prevent initial focus, and escapeDeactivates which can now alternately be a function that returns a boolean instead of a straight boolean.

8.6.0

Minor Changes

• 5292ae8:
  • Adding support for new focus-trap options from focus-trap v6.5.0: checkCanFocusTrap(), onPostActivate(), checkCanReturnFocus(), and onPostDeactivate().
  • Adding support (bug fix) for existing focus-trap setReturnFocus option that had thus far been ignored, with focus-trap-react always returning focus to the previously-focused element prior to activation regardless of the use of the setReturnFocus option. The option is now respected the same as it is when using focus-trap directly.

Patch Changes

• 24704c7: Bump focus-trap dependency to 6.5.1 for bug fix to onPostDeactivate.

8.5.1

Patch Changes

• b8d7071: Bump focus-trap dependency to 6.5.0 to get new features

8.5.0

Minor Changes

• 6ee37fb: Bump focus-trap from 6.3.0 to 6.4.0. There should be no changes in behavior as a result of this upgrade.

8.4.2

Patch Changes

• f9a6d1a: Throw an error if a Fragment is given as the child container (currently, it appears to work, but the trap is actually not activated because focus-trap can't find the DOM element for the Fragment "container"). (Fixes #268)

8.4.1

Patch Changes

• a4c3105: Update PropTypes for clickOutsideDeactivates to match latest focus-trap.

8.4.0

Minor Changes

• 8d58bc8: Bump focus-trap to v6.3.0

8.3.2

Patch Changes

• 53fa056: Update focus-trap dependency to new patch release v6.2.2 for bug fix to multi-container traps.

8.3.1

Patch Changes

• 5d70831: Bump focus-trap to 6.2.1 for bug fixes.

8.3.0

Minor Changes

• c4e4837: Remove the need for a child, update typings, update docs:
  • Remove the need for a child in <FocusTrap /> when containerElements is used. The child was already being ignored anyway (when containerElements is used; if the prop is not used, then a single child is still required).
  • Update the typings related to the children prop to make it optional. Prop-types already had children as optional, however the use of React.Children.only() in all cases was still forcing the presence of a single child. That's no longer the case.
  • Add additional notes about the use of the containerElements prop in the documentation.

Patch Changes

• 0836c6d: Fixing a bug where the focus trap may not have been set before it is unmounted #184