fix(deps): Update dependency focus-trap to v7 #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^6.2.2->^7.6.5Release Notes
focus-trap/focus-trap (focus-trap)
v7.6.5Compare Source
Patch Changes
d51ad78: Allow activation element in shadow DOM to be auto-focused after trap is deactivatedv7.6.4Compare Source
Patch Changes
bb47f7a: Remove engine requirement that crept intopackage.json. Sorry about that! (#1343)v7.6.3Compare Source
Patch Changes
0a9b746: Prevent a previous focus trap that is manually paused from being automatically unpaused when the current trap is deactivated. Also prevent a paused trap that is not at the top of the stack from being unpaused.v7.6.2Compare Source
Patch Changes
d4a4c34: Replace findIndex with native implementation - [Closes #1305](#1305v7.6.1Compare Source
Patch Changes
fc5910d: Fix fallbackFocus not used when initialFocus is selector to non-existent node (#1218)v7.6.0Compare Source
Minor Changes
8aeacee: MoveEscapekey handler to target phase to allow more control inescapeDeactivates(#1247)v7.5.4Compare Source
Patch Changes
680f6e8: Fix issue with not being able to cycle back to the start from the last element if there is a focusable web component inside the focus-trap ((#1068)[#1068])v7.5.3Compare Source
Patch Changes
203b322: Fix missing typings for initialFocus option (#1060)v7.5.2Compare Source
Patch Changes
b73eb02: Remove references toArray.prototype.findLast()not well supported in Safari (#996)v7.5.1Compare Source
Patch Changes
d9e2546: Fix possible exception in newTabbable.getTabIndex()when initializing trapv7.5.0Compare Source
Minor Changes
5e2f913: Adds support for nodes with a positive tabindex in single-container traps only (#375)v7.4.3Compare Source
Patch Changes
134678b: Ensure focus is kept inside the trap when focused element is removed from the DOM (focus-trap/focus-trap-react#962)v7.4.2Compare Source
Patch Changes
db62ce3: Clicking on open shadowDOM components within a focus trap's container whenclickOutsideDeactivates=trueshould not deactivate the focus trap. (#959)v7.4.1Compare Source
Patch Changes
4f720ff: Bump tabbable to v6.1.2 for nwsapi patchv7.4.0Compare Source
Minor Changes
da97007: Added new onPost/Pause and onPost/Unpause hooks when un/pausing a trap (also called when auto-un/paused as a result of de/activating a second trap while another is currently active). (focus-trap-react#948)v7.3.1Compare Source
Patch Changes
a00cfa5: Bump tabbable to v6.1.1 for JSDom fixesv7.3.0Compare Source
Minor Changes
ae7129d: Bump tabbable to v6.1.0 adding support for the new HTMLinertattribute in browsers that support it (NOTE: FireFox does not support it at this time). Also fixes a bug. See tabbable CHANGELOG for more info.Patch Changes
a27ad58: Fix incorrect behavior ofreturnFocusOnDeactivateoption when set to true (or defaulted to true) along withclickOutsideDeactivates=trueand the outside click that deactivates is on a focusable node. Focus was remaining on that node instead of returning to the node focused just prior to activation. (#893)v7.2.0Compare Source
Minor Changes
b0482af: Add newisKeyForward()andisKeyBackward()options (#612)v7.1.0Compare Source
Minor Changes
88cc9bc: Provide newtrapStackoption to make it possible to coordinate auto-activation/pausing between multiplefocus-trapinstances on the same page.Patch Changes
4f97b38: Bump tabbable to v6.0.1 for a bug fix. See tabbable's changelog for more details.f13de76: Mention special Safari setting to enable normal DOM-based tab order in README. #783v7.0.0Compare Source
Major Changes
5b64423: Revised and clarified official browser support (still as broad and deep as reasonably possible).47f62ac: 🚨 Breaking: Tabbable dependency has been updated to v6.0.0 and contains a breaking change related to detached nodes with its defaultdisplayChecksetting. See tabbable's changelog for more information.5b64423: 🚨 Breaking: Dropped support of IE browsers, all versions.v6.9.4Compare Source
Patch Changes
f68882e: Fix docs and typings to clarify that initialFocus, fallbackFocus, and setReturnFocus options can be functions that also return selector strings.v6.9.3Compare Source
Patch Changes
8a8b1f1: Bump tabbable to v5.3.3 to pick up a small bug fix to web component (shadow DOM) support.v6.9.2Compare Source
Patch Changes
ef0ce48: Handle unexpected param (true) passed as the value for theinitialFocus,fallbackFocus, andsetReturnFocusoptions: Ignore and perform default behavior.v6.9.1Compare Source
Patch Changes
83262a7: Bumps tabbable to v5.3.2 to pick-up a fix todisplayCheck=full(default) option behavior that caused issues with detached nodes.v6.9.0Compare Source
Minor Changes
2a57e4b: Add newtrap.activeandtrap.pausedreadonly state properties on the trap so that the trap's active/paused state can be queried.Patch Changes
8fd49df: Fixed bug whereclickOutsideDeactivatehandler would get called on the 'click' event even if the node clicked was in the trap. As with 'mousedown' and 'touchstart' events where this option is also used, the handler should only get called if the target node is outside the trap.c32c60a: Fixed: onDeactivate, onPostDeactivate, and checkCanReturnFocus options originally given to createFocusTrap() were not being used by default when callingtrap.deactivate({...})with an option set even if that option set didn't specify any overrides of these options.v6.8.1Compare Source
Patch Changes
7c86111:^5.3.1(fixing previous update which was incorrectly set to5.3.0).tabbableOptionsnot being used in all internal uses of tabbable APIs.displayCheckoption intabbableOptionstypings and pass it through to tabbable APIs.v6.8.0Compare Source
Minor Changes
21458c9: Bumps tabbable to v5.3.0 and includes all changes from the past v6.8.0 beta releases. The big new feature is opt-in Shadow DOM support in tabbable, and a newgetShadowRoottabbable option exposed in a newtabbableOptionsfocus-trap config option.v6.7.3Compare Source
Patch Changes
ab20d3d: Fix issue with focusing negative tabindex node and then tabbing away when this node is not the last node in the trap's container ((#611)[#611])v6.7.2Compare Source
Patch Changes
c932330: Fixed bug where tabbing forward from an element with negative tabindex that is last in the trap would result in focus remaining on that element (565)Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate using a curated preset maintained by
. View repository job log here