#community-help

Implementing Instantsearch on Custom Input Box Issue

TLDR AK encountered issues with instantsearch on a custom input box. Jason resolved it by having instantsearch use Bubble's own input box.

16mo

Join the chat

Sep 03, 2022 (16 months ago)

Photo of md5-f2442b8542de1fe5a9703111f2002950

AK

10:30 AM

I am implementing the instantsearch on a custom inputbox, and for some reason it keeps going to the upper-left corner of the page

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

06:09 PM

Had a chat about this over a call. It was an issue with instantsearch rendering it’s own input box by default. Had to get it to to use the input box that Bubble was rendering instead.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Troubleshooting Typesense Setup and Understanding Facets and Keywords

Demitri encountered errors when exploring Typesense for the first time. Jason guided them through troubleshooting and discussed facets, keyword settings, and widget configurations. Helin shared a Python demo app and its source code to help Demitri with their project.

21mo

Custom MenuSelect Component Error with Different Facet Lists

KARTHICK and Uma face the same issue with a custom menuselect component. Jason suggests asking in the instantsearch GitHub repo.

6mo

Resolving Issue with Instantsearch Sort_by in React

Edward had a problem with sorting functionality in a React component using Algolia's InstantSearch. Jason recommended a potential solution for specifying index names which resolved the issue.

19mo