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
I updated the npm dependency to the latest version (5.1.3), and the plugin stopped working.
When I am debugging autocomplete.js I see that this expression always evaluates to false: keypressCounter === savedKeypressCounter in the "startFetch" function.
Ok, sounds like we had a bug on our end then. Your component was rendered as part of a material component in our form. We decided to use a drop-down instead for now. Thank you very much for looking in to this, and for creating this awesome plugin.
I updated the npm dependency to the latest version (5.1.3), and the plugin stopped working.
When I am debugging autocomplete.js I see that this expression always evaluates to false:
keypressCounter === savedKeypressCounter
in the "startFetch" function.This is how we are setting up our autocomplete:
What are we doing wrong?
This was tested on mac os v10.13.6 on a chrome Version 78.0.3904.70 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: