Open
Conversation
Daniel-KM
pushed a commit
to Daniel-KM/Omeka-S-module-AdvancedSearch
that referenced
this pull request
Sep 29, 2021
Daniel-KM
pushed a commit
to Daniel-KM/Omeka-S-module-AdvancedSearch
that referenced
this pull request
Oct 20, 2021
|
Thanks for the fix. However is there anyway the blur function could be aware of the target of the click, and not hide the autocomplete if it is the target? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #809. If someone is a "slow clicker" it can happen that the autocomplete selection is closed instead of triggering the click event. You can try this when holding the left mouse button for a short time, this increases the timeout a bit to make it more likely that the click event is triggered.