v6.4.0

Minor Changes

• 26a1d80: Enable CSS selector matching for whether an element is in an inert subtree ([inert] *).

  This was previously disabled due to JSDOM's CSS selector engine being incompatible with this selector, and throwing all the results off. Instead, tabbable would perform manual checks for an element being in an inert subtree. The CSS selector issue appears to have been fixed in recent JSDOM versions (at least 26), so this version reintroduces the selector fast path.

v6.3.0

Minor Changes

• fae1e50: feat: add 'full-native' displayCheck option, utilising Element#checkVisibility

v6.2.0

Minor Changes

• 18a093f: Add new getTabIndex() API which enables Focus-trap to determine tab indexes in the same way as Tabbable when necessary (see focus-trap#974).

v6.1.2

Patch Changes

• b39b217: Pin jsdom downstream dependency nwsapi to v2.2.2 while awaiting fix (#982)

v6.1.1

Patch Changes

• 97373cc: Fix JSDom not supporting HTMLElement.inert and HTMLElement.contentEditable APIs, and not supporting CSS selector ':not([inert *])' resulting in no nodes found and "focus-trap must have at least one tabbable node..." error in focus-trap.

v6.1.0

Minor Changes

• 1756c90: Add support for new inert attribute (#292)

Patch Changes

• b8c7550: Fix a corner case where a node's root node can be itself, indicating detachment from the DOM, leading to a crash in isHidden() -> isNodeAttached() -> getRootNode() if not handled properly (focus-trap-react #905)

v6.0.1

Patch Changes

• 0aab1e3: Fix crash with tabbable scoped table header elements (#832)

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.