You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something to keep in mind, that we're aware of and are still trying to resolve, is that our implementation of Autocomplete is still on version 0.38.x. So it's possible that the autocomplete templates that we ship with need some overhaul for this onStateChange functionality to be available.
The good news is that our templates are basically just files that we store all the javascript on, and can be completely overwritten, but I also know and admit is extra work on the plugin user's side. I also know that I've done my own override from our plugin for a client and got them updated to Autocomplete 1.x in the process.
In case curious, one big hurdle is that with version 0.38.x we were able to specify a selector for what to attach the Autocomplete UI to out of box, like common pattern WordPress search forms. With version 1.x, they moved to looking for something like <div id="autocomplete"></div> for their DOM selecting, and that's much less easy to consistently find, if find at all, for out-of-box Autocomplete integration.
Is your feature request related to a problem? Please describe.
Need to trigger a polyfill after state change.
Describe the solution you'd like
Open the onStateChange parameter in your custom instance of window.autocomplete
https://www.algolia.com/doc/ui-libraries/autocomplete/core-concepts/state/#listening-to-state-changes
Additional context
Perhaps this is already available, but I cannot find if after digging through documentation.
The text was updated successfully, but these errors were encountered: