Fix long click issue #342
Closed
Fix long click issue #342
Conversation
This file contains 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
d-lan1
force-pushed
the
FixLongClickIssue
branch
from
48fb3d6
to
bd5f047
Compare
d-lan1
force-pushed
the
FixLongClickIssue
branch
from
ca4f7d1
to
4d50be3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When clicking(mousedown) on the autocomplete recommendations for slightly longer than usual, the drop down disappears and no item is selected. I would expect the dropdown to remain open until the click is released OR as soon as the mousedown event has fired for the item to be selected.
In this pull request I have fixed the above issue. In addition to this I have also removed the quotation marks from the npm scripts as this was causing issues with execution on my windows machine.