Skip to content

Releases: focus-trap/focus-trap-react

v10.0.0

24 Aug 18:54
81de828
Compare
Choose a tag to compare

Major Changes

  • af69c14: 🚨 Breaking: Underlying tabbable dependency has been updated to v6.0.0 and contains a breaking change related to detached nodes with its default displayCheck setting. See tabbable's changelog for more information.
    • The focus-trap dependency has also be updated to v7.0.0 but only contains the underlying tabbable changes.
    • The tabbableOptions.displayCheck prop type has been updated to include the new "legacy-full" option.
  • 018732c: 🚨 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.
  • 018732c: Revised and clarified official browser support (still as broad and deep as reasonably possible).

Patch Changes

  • b0bbbd4: Update README with a note about the children prop stating that the trap requires a single child, and that if a component is used, it must be a functional component that forwards refs.

v9.0.2

18 Jun 20:22
9d6fed3
Compare
Choose a tag to compare

Patch Changes

  • 4d8e041: Fix an issue when running in strict mode which has React immediately unmount/remount the trap, causing it to deactivate and then have to reactivate (per existing component state) on the remount. #720

v9.0.1

13 Jun 21:16
52f57ff
Compare
Choose a tag to compare

Patch Changes

  • 2d6cd9b: Add explicit dependency on tabbable since the source directly requires it.

v9.0.0

10 Jun 00:20
7615185
Compare
Choose a tag to compare

Major Changes

  • 4a77d87: Stop using the infamous findDOMNode() on provided containerElements.
    • There seems to have been no good reason for this as this prop, if specified, is already required to be an array of HTMLElement references, which means these nodes have already been rendered (if they were once React elements). There appears to have been no remaining need for this API.
    • Furthermore, the minimum supported version of React is now 16.3 as it technically has been for a while now since that is the version that introduced callback refs, which we've been using for quite some time now (so this bump will hopefully not cause any ripples).

v8.11.3

09 Jun 23:59
7fd489c
Compare
Choose a tag to compare

Patch Changes

  • 9947461: Bump focus-trap dependency to v6.9.4 to get typings fix.
  • 519e5a5: Fix setReturnFocus option as function not being passed node focused prior to activation.

v8.11.2

25 May 21:54
e24502b
Compare
Choose a tag to compare

Patch Changes

  • 7547d93: Bumps focus-trap to v6.9.3 to pick-up some small bug fixes from underlying tabbable.

v8.11.1

06 May 21:22
ab8cd0a
Compare
Choose a tag to compare

Patch Changes

  • 040813a: Bumps focus-trap to v6.9.1 to pick-up a fix to tabbable in v5.3.2 regarding the displayCheck=full (default) option behavior that caused issues with detached nodes.

v8.11.0

28 Apr 21:48
0beb7f8
Compare
Choose a tag to compare

Minor Changes

  • 7495680: Bump focus-trap to v6.9.0 to get bug fixes and new features to help fix some bugs.

Patch Changes

  • 7495680: Fix onDeactivate, onPostDeactivate, and checkCanReturnFocus options not being called consistently on deactivation.
  • 7495680: Fix focus not being allowed to remain on outside node post-deactivation when clickOutsideDeactivates is true or returns true.

v8.10.0

22 Apr 14:46
957d1e5
Compare
Choose a tag to compare

Minor Changes

  • 659d44e: Bumps focus-trap to v6.8.1. The big new feature is opt-in Shadow DOM support in focus-trap (in tabbable), and new tabbable options exposed in a new focusTrapOptions.tabbableOptions configuration option.

v8.9.2

12 Feb 18:01
ed75765
Compare
Choose a tag to compare

Patch Changes

  • 83e283c: Update focus-trap to v6.7.3 for bug fix related to elements with a negative tabindex.