Restore select to its original position when destroying #1250
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
|
To be clear on the issue, currently when you fire the |
|
Good catch. I'll test and merge this tomorrow. |
caseyjhol
added a commit
that referenced
this pull request
Jan 12, 2016
Restore select to its original position when destroying
|
Awesome, thanks for merging. |
|
This fixed my issue too! Thanks! |
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.
In my opinion, when destroying the bootstrap-select element, it should restore the select to its original position. In 1.7.7 (where I first noticed the issue) it was only an issue with the mobile version, but since
this.$elementis now always appended tothis.$newElement, it's an issue in general.