François Chalifour

The `NumericMenu` component reads from the search state and therefore needs to contain the `multiRange` value passed via the search state. In the sandbox you sent, it expects the range...

Thanks for the report. We rely on [`scrollIntoViewIfNeeded`](https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoViewIfNeeded) if the browser supports it, and otherwise fallback to [`scrollIntoView`](https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView): https://github.com/algolia/autocomplete/blob/e81c31fbc89ad72229ed84b0318873d442ceb19b/packages/autocomplete-core/src/onKeyDown.ts#L36-L40 The `scrollIntoViewIfNeeded` method [is not compatible with Firefox](https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoViewIfNeeded#browser_compatibility), which is why...

Thanks for opening the issue. Internally we compute the top and left positions of the panel based on the search box', and apply them on the `style` of the element...

> Do we have other use cases in mind for the Layout API? For example, would we imagine packaging the [templates from the classic theme](https://autocomplete.algolia.com/docs/autocomplete-theme-classic#templates), or providing an out-of-the-box preview...

I updated the API to use our new Component API: ```tsx /** @jsx h */ import { autocomplete } from '@algolia/autocomplete-js'; import { NavigationCommands, SearchByAlgolia, } from '@algolia/autocomplete-layout-classic'; import {...

Putting "On Hold" because we de-prioritized the Layout API.

Thanks for the bug report @jgarrow. > 4. Scroll back up to see the search bar input. The search bar input should be blank. I think you meant "The search...

Yeah, it should fill the query with the item's value. We'll investigate why this happens. Thanks again.

Thanks for the report—focus trap is on our list! We plan to implement it in a [similar way as in DocSearch](https://github.com/algolia/docsearch/blob/bf18c7374e66581bd0b08b19f7a61b4a30bdcef3/packages/docsearch-react/src/useTrapFocus.ts).

Thanks for the report @heyuxian! That's a tricky case because the panel is supposed to close when the input loses focus, and a `select` element blurs the input on click....