Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling .abort() prevents future queries from being made #211

Closed
simplenotezy opened this issue Jan 25, 2020 · 2 comments
Closed

Calling .abort() prevents future queries from being made #211

simplenotezy opened this issue Jan 25, 2020 · 2 comments

Comments

@simplenotezy
Copy link

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.

@simplenotezy
Copy link
Author

Also talked about here twitter/typeahead.js#1114

@simplenotezy
Copy link
Author

I believe this is the cause: #212

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant