Haz

That's expected. If you check the WAI-ARIA pattern, you'll see that the behavior should be different when the radio group is contained in a toolbar. The same applies to other...

Thanks for reporting. As a workaround, you can add `onScroll={popover.render}` to the scrollable element.

@sarayourfriend I have a POC here: https://codesandbox.io/s/ariakit-component-stores-forked-248do5?file=/src/dom/disclosure-store.ts `useSelectStore` returns a stable `store` object with updater functions and nested hooks. `store.useState()` returns a `state` using `useSyncExternalStore`.

> I can see this working out, but my only reservation is with the `store.useState()` method and how verbose that could end up being (forces the creation of listeners for...

It doesn't work because the underlying input element is controlled (by the combobox state's `value` and `setValue` properties). We can potentially support this by listening to the form's `reset` event...

That's expected since the listbox element is not tabbable. And focusing on any item would immediately move focus to the combobox input, preventing users from reaching the Apply button. I...

There's also: ```js Node.isJSDocable(declaration) ```

Have you tried https://beta.nextjs.org/docs/api-reference/segment-config?

The type definitions for `getInputProps` should be less restrictive and accept any prop in addition to its own props. Then, return the combined object shape and let the component handle...

> 1. `as` prop: it requires a little bit more code changes to add/remove a tooltip on an element [There's a lot of problems with the `as` prop](https://youtu.be/_kyv3tnQKfg?t=949), but I...