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 noticed on the network tab that multiple queries are being made, e.g. when user is typing "home", and then swifly after changes query to "homes", the first query "home" might still be pending.
I'd expect the bloodhound engine to .abort() previous sent requests that have no been finished, since search query has been changed - after all, I guess theres no reason for the request to finish?
I have tried implementing my own logic using transport property, but if .abort() is being called on an active remote query, it will never fire again, no matter what input is typed into the typeahead. Very strange behavior.
The text was updated successfully, but these errors were encountered:
I noticed on the network tab that multiple queries are being made, e.g. when user is typing "home", and then swifly after changes query to "homes", the first query "home" might still be pending.
I'd expect the bloodhound engine to .abort() previous sent requests that have no been finished, since search query has been changed - after all, I guess theres no reason for the request to finish?
I have tried implementing my own logic using
transport
property, but if.abort()
is being called on an active remote query, it will never fire again, no matter what input is typed into the typeahead. Very strange behavior.The text was updated successfully, but these errors were encountered: