Haroen Viaene

Thanks a lot for this! Have you tried adding a test for this behaviour? Otherwise this should be good to merge

Thanks a lot for your contribution! This is now in 1.17.1 :)

To start unpacking this behaviour, it seems to be linked to this line: https://github.com/algolia/autocomplete/blob/next/packages/autocomplete-core/src/onKeyDown.ts#L146 where somehow getActiveItem returns `null`, although I don't know how that can happen

I believe that redirects may rely on the request not being cancelled (at least available in the results), but it should indeed prevent to reopen though

There's no autocomplete-input testid in that example, do you have a full reproduction?

FYI, this is a warning, not an error. we have not yet updated the main example, but https://github.com/algolia/autocomplete/issues/950#issuecomment-1110688407 gives a user land solution

What I suggest as an improvement is to put the state of the checkbox as checked as soon as a user clicks, but also put it as `disabled={true}`. Once the...

It depends. This is not a top priority right now, as you say, it's perfectly doable with connectors, maybe as a guide. If you have the code for dealing with...

Yes, but it's not as simple as just debouncing, since that would be hurting the users that actually *do* have a good connection. In any case, that's probably something that...

@OArnarsson, you can call `instantSearchInstance.setUiState({ myIndex: { refinementList: { attribute: [1,2]}}})`. I'm not sure if we expose the InstantSearch instance yet officially though, but otherwise you can read from the...