Add selectOnTab config option #371
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
|
+1 to selectOnTab default to false |
|
+1 Have an interaction where hitting the tab should not cause selection. |
brianreavis
added a commit
that referenced
this pull request
Apr 30, 2014
Add selectOnTab config option
|
Thanks for this – I agree with you. I went a bit too far when working to please the other crowd. |
|
Glad I saw this now, wandering why when I press tab it tabs to the next input element and doesn't select the selectize input |
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.
Adds a new config option called "selectOnTab" to make the functionality added in #258 optional since it is undesirable behavior in the event that there are many, potentially not required, Selectize controls in a single form (as just tabbing through them will cause the first option to be selected in each).
I ended up defaulting it to false as this was the "default" behavior prior to 0.9.0.