Skip to content

chore(deps): Bump focus-trap from 7.8.0 to 8.0.0 in /build/frontend-legacy#58160

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/build/frontend-legacy/focus-trap-8.0.0
Open

chore(deps): Bump focus-trap from 7.8.0 to 8.0.0 in /build/frontend-legacy#58160
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/build/frontend-legacy/focus-trap-8.0.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 7, 2026

Bumps focus-trap from 7.8.0 to 8.0.0.

Release notes

Sourced from focus-trap's releases.

v8.0.0

Major Changes

  • b6ea4b5: Breaking: Fixed a long-standing bug where onPostActivate() would be called before the initial focus node was focused and the trap was fully activated. (#1747)
    • By default (and for many years now), a trap delays setting focus to the initial focus node to the next frame (setTimeout(0)) but wasn't delaying calling onPostActivate() until after that delay.
    • With the new isolateSubtrees='aria-hidden' option, the currently-focused node's container (a non-subtree being "disabled") would get hidden before the delay was up, resulting in Chrome preventing the effect of aria-hidden on that subtree with a warning in the console due to the container being hidden still containing focus (e.g. the "activate trap" button).
    • With the fix, subtree isolation and the call to onPostActivate() await the initial focus delay (if there is one, which is default behavior; remove it with delayInitialFocus=false) before being applied/called.
    • This may cause tests to fail, requiring the addition of slight delays before testing a given state (e.g. await waitFor(() => expect(initialFocusNode).toBeFocused()).
    • It may also disrupt current assumptions about the state of the initial focus node in code that runs in your onPostActivate() handler (prior to this change, that node would not be focused yet; after this change, it will be focused).
Changelog

Sourced from focus-trap's changelog.

8.0.0

Major Changes

  • b6ea4b5: Breaking: Fixed a long-standing bug where onPostActivate() would be called before the initial focus node was focused and the trap was fully activated. (#1747)
    • By default (and for many years now), a trap delays setting focus to the initial focus node to the next frame (setTimeout(0)) but wasn't delaying calling onPostActivate() until after that delay.
    • With the new isolateSubtrees='aria-hidden' option, the currently-focused node's container (a non-subtree being "disabled") would get hidden before the delay was up, resulting in Chrome preventing the effect of aria-hidden on that subtree with a warning in the console due to the container being hidden still containing focus (e.g. the "activate trap" button).
    • With the fix, subtree isolation and the call to onPostActivate() await the initial focus delay (if there is one, which is default behavior; remove it with delayInitialFocus=false) before being applied/called.
    • This may cause tests to fail, requiring the addition of slight delays before testing a given state (e.g. await waitFor(() => expect(initialFocusNode).toBeFocused()).
    • It may also disrupt current assumptions about the state of the initial focus node in code that runs in your onPostActivate() handler (prior to this change, that node would not be focused yet; after this change, it will be focused).
Commits
  • d9155b4 Version Packages (#1755)
  • b6ea4b5 #1747 Fix aria-hidden blocked when isolating subtrees due to initial focus ...
  • 186e6b4 [DEPENDABOT]: Bump @​types/node from 25.0.9 to 25.0.10 (#1750)
  • 42e838b [DEPENDABOT]: Bump rollup from 4.55.3 to 4.57.0 (#1752)
  • 29eba6b [DEPENDABOT]: Bump @​typescript-eslint/eslint-plugin from 8.53.1 to 8.54.0 (#1...
  • 0c94ec0 [DEPENDABOT]: Bump globals from 17.0.0 to 17.2.0 (#1753)
  • f274bf2 [DEPENDABOT]: Bump prettier from 3.8.0 to 3.8.1 (#1754)
  • a5d0048 [DEPENDABOT]: Bump lodash from 4.17.21 to 4.17.23 (#1746)
  • 9f5940b [DEPENDABOT]: Bump @​typescript-eslint/eslint-plugin from 8.53.0 to 8.53.1 (#1...
  • f936d43 [DEPENDABOT]: Bump rollup from 4.55.1 to 4.55.3 (#1741)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [focus-trap](https://github.com/focus-trap/focus-trap) from 7.8.0 to 8.0.0.
- [Release notes](https://github.com/focus-trap/focus-trap/releases)
- [Changelog](https://github.com/focus-trap/focus-trap/blob/master/CHANGELOG.md)
- [Commits](focus-trap/focus-trap@v7.8.0...v8.0.0)

---
updated-dependencies:
- dependency-name: focus-trap
  dependency-version: 8.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested review from a team as code owners February 7, 2026 02:13
@dependabot dependabot bot requested review from sorbaugh, susnux and szaimen and removed request for a team February 7, 2026 02:13
@github-actions github-actions bot enabled auto-merge February 7, 2026 04:02
@susnux
Copy link
Contributor

susnux commented Feb 7, 2026

might break with nc vue, as we likely need both to use the same major version.
At least there were problems recently, cc @ShGKme

@ShGKme
Copy link
Contributor

ShGKme commented Feb 7, 2026

Seems mostly backward compatible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants