chore(deps): bump @ariakit/react from 0.4.19 to 0.4.26 in /react

[dependabot]

Bumps @ariakit/react from 0.4.19 to 0.4.26.

Release notes

Sourced from @​ariakit/react's releases.

@​ariakit/react-core@​0.4.26

This version focuses on bug fixes across Dialog, Portal, Radio, Combobox, and MenuButton, along with improvements to how portals behave inside fullscreen elements, how dialogs handle events in popup windows, and how Radio groups automatically generate unique name attributes.

Fixed events not handled in popup windows

Dialog and components that extend it, such as Menu and Popover, now handle events correctly when rendered in a popup window opened via window.open(). hideOnEscape, hideOnInteractOutside, and focus restoration now use the content element's ownerDocument instead of the main window's document for event listeners.

Fixed Portal not rendering inside fullscreen elements

Portal was always appended to document.body, which made it invisible when an ancestor element entered fullscreen mode via the Fullscreen API. Portals are now automatically moved to document.fullscreenElement when it's active, and back to document.body when fullscreen is exited.

Auto-generated name attribute for Radio

Radio now automatically uses the RadioGroup store's id as the default name attribute when no explicit name prop is provided. This ensures consecutive RadioGroup components have unique names, preventing the browser from treating all radio inputs as a single group and fixing Tab navigation and form submission issues.

Other updates

• Fixed Combobox pressing Enter from submitting a parent form when the popover is open but has no matching items.
• Fixed Dialog not removing data-enter when closed after using the render prop to wrap the dialog element in an outer element.
• Fixed Dialog not restoring focus to the disclosure element when the dialog was opened and closed quickly in succession.
• Fixed MenuButton aria-haspopup attribute changing from "menu" to "dialog" when opening a menu that contains a combobox.
• Fixed render prop merging when the rendered element passes falsy className or event handler values such as undefined or null.
• Fixed Math.random() being called unconditionally when creating composite stores (useTabStore, useComboboxStore, useSelectStore, etc.), even when an explicit id prop was provided. This was causing Next.js build errors with cacheComponents enabled.
• Updated dependencies: @ariakit/core@0.4.20

@​ariakit/react@​0.4.26

This version focuses on bug fixes across Dialog, Portal, Radio, Combobox, and MenuButton, along with improvements to how portals behave inside fullscreen elements, how dialogs handle events in popup windows, and how Radio groups automatically generate unique name attributes.

Fixed events not handled in popup windows

Dialog and components that extend it, such as Menu and Popover, now handle events correctly when rendered in a popup window opened via window.open(). hideOnEscape, hideOnInteractOutside, and focus restoration now use the content element's ownerDocument instead of the main window's document for event listeners.

Fixed Portal not rendering inside fullscreen elements

Portal was always appended to document.body, which made it invisible when an ancestor element entered fullscreen mode via the Fullscreen API. Portals are now automatically moved to document.fullscreenElement when it's active, and back to document.body when fullscreen is exited.

Auto-generated name attribute for Radio

Radio now automatically uses the RadioGroup store's id as the default name attribute when no explicit name prop is provided. This ensures consecutive RadioGroup components have unique names, preventing the browser from treating all radio inputs as a single group and fixing Tab navigation and form submission issues.

Other updates

• Fixed Combobox pressing Enter from submitting a parent form when the popover is open but has no matching items.
• Fixed Dialog not removing data-enter when closed after using the render prop to wrap the dialog element in an outer element.
• Fixed Dialog not restoring focus to the disclosure element when the dialog was opened and closed quickly in succession.
• Fixed MenuButton aria-haspopup attribute changing from "menu" to "dialog" when opening a menu that contains a combobox.
• Fixed render prop merging when the rendered element passes falsy className or event handler values such as undefined or null.
• Fixed Math.random() being called unconditionally when creating composite stores (useTabStore, useComboboxStore, useSelectStore, etc.), even when an explicit id prop was provided. This was causing Next.js build errors with cacheComponents enabled.
• Updated dependencies: @ariakit/react-core@0.4.26

... (truncated)

Changelog

Sourced from @​ariakit/react's changelog.

0.4.26

This version focuses on bug fixes across Dialog, Portal, Radio, Combobox, and MenuButton, along with improvements to how portals behave inside fullscreen elements, how dialogs handle events in popup windows, and how Radio groups automatically generate unique name attributes.

Fixed events not handled in popup windows

Dialog and components that extend it, such as Menu and Popover, now handle events correctly when rendered in a popup window opened via window.open(). hideOnEscape, hideOnInteractOutside, and focus restoration now use the content element's ownerDocument instead of the main window's document for event listeners.

Fixed Portal not rendering inside fullscreen elements

Portal was always appended to document.body, which made it invisible when an ancestor element entered fullscreen mode via the Fullscreen API. Portals are now automatically moved to document.fullscreenElement when it's active, and back to document.body when fullscreen is exited.

Auto-generated name attribute for Radio

Radio now automatically uses the RadioGroup store's id as the default name attribute when no explicit name prop is provided. This ensures consecutive RadioGroup components have unique names, preventing the browser from treating all radio inputs as a single group and fixing Tab navigation and form submission issues.

Other updates

• Fixed Combobox pressing Enter from submitting a parent form when the popover is open but has no matching items.
• Fixed Dialog not removing data-enter when closed after using the render prop to wrap the dialog element in an outer element.
• Fixed Dialog not restoring focus to the disclosure element when the dialog was opened and closed quickly in succession.
• Fixed MenuButton aria-haspopup attribute changing from "menu" to "dialog" when opening a menu that contains a combobox.
• Fixed render prop merging when the rendered element passes falsy className or event handler values such as undefined or null.
• Fixed Math.random() being called unconditionally when creating composite stores (useTabStore, useComboboxStore, useSelectStore, etc.), even when an explicit id prop was provided. This was causing Next.js build errors with cacheComponents enabled.
• Updated dependencies: @ariakit/react-core@0.4.26

0.4.25

Clicking outside no longer restores focus to the disclosure element

Dialog and components that extend it (such as Menu and Popover) no longer restore focus to the disclosure element when the dialog is closed by clicking or right-clicking outside. This aligns with native HTML <dialog> and popover behavior where trigger buttons don't receive focus when you interact outside.

Focus is still restored normally when the dialog is closed by other means, such as pressing Escape, selecting a menu item, or calling store.hide() programmatically. In these cases the disclosure element is now focused with default browser scrolling instead of preventScroll.

Improved Safari focus behavior for buttons, checkboxes, and radio buttons

On Safari, buttons, checkboxes, and radio buttons don't receive focus on mousedown like other browsers. Previously, this was handled by manually focusing the element in a mousedown handler. Now, an explicit tabIndex attribute is set on these elements in Safari, which causes the browser to focus them natively. This results in more predictable focus behavior and fewer timing-sensitive workarounds.

Other updates

• Fixed a race condition in Dialog where the deferred auto-focus could steal focus from the disclosure element after the dialog was closed.
• Fixed formStore.setError() and formStore.setFieldTouched() failing to set values on nested array field paths such as items.0.name.
• Fixed SelectItem store item children property reflecting the value prop instead of the actual rendered text content.
• Fixed MenuButton to preserve accessibleWhenDisabled behavior when composed with a rendered Button.
• Fixed Menu with modal and getPersistentElements so focusing a persistent MenuButton doesn't immediately move focus back to the menu.
• Fixed TabPanel not re-evaluating tabbable children when the panel becomes visible.
• Fixed components not dropping their internal aria-labelledby when aria-label is passed.
• Updated dependencies: @ariakit/react-core@0.4.25

0.4.24

... (truncated)

Commits

• 9d3b642 Publish (#5737)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​ariakit/react since your current version.

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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉