Repository navigation
Releases: focus-trap/tabbable
Releases · focus-trap/tabbable
Release list
v6.5.0
Minor Changes
- 8e6c074: Add support for
<area>elements with anhrefattribute (image map hotspots),
Patch Changes
- f656723: Treat elements with
visibility: collapseas hidden, the same wayvisibility: hiddenis already handled, so they are no longer considered tabbable or focusable. This matches browser behavior, wherecollapsehides an element (outside of table rows/columns) just likehidden.
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'
displayCheckoption, 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
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
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
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