Change behavior of autocomplete #112
Merged
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
| @@ -253,7 +253,8 @@ var TypeaheadView = (function() { | |||
| hint = this.inputView.getHintValue(); | |||
|
|
|||
| if (hint !== '' && query !== hint) { | |||
| this.inputView.setInputValue(hint); | |||
| suggestion = this.dropdownView.getFirstSuggestion(); | |||
There was a problem hiding this comment.
.getHighlightedOrFirstSuggestion()?
There was a problem hiding this comment.
The hint will always be the the first suggestion in the dropdown.
There was a problem hiding this comment.
What if I arrow up or down?
There was a problem hiding this comment.
Oh, then it changes the value, so there's no hint. Carry on…ship it.
|
I like this change, regardless of when it ships. |
jharding
added a commit
that referenced
this pull request
Mar 14, 2013
Change behavior of autocomplete
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.
See #49 for details. Not 100% sure I want to ship this in v0.9.0.