-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(model): correctly set activeindex of select element in a new v-model #6910
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
gebilaoxiong
force-pushed
the
fix-select-active-index
branch
from
October 26, 2017 13:33
1519c9c
to
0fbe760
Compare
gebilaoxiong
changed the title
fix($browser): correctly set select activeIndex in v-model
fix(model): correctly set activeindex of select element in a new v-model
Oct 26, 2017
@@ -546,4 +546,30 @@ describe('Directive v-model select', () => { | |||
expect(spy).not.toHaveBeenCalled() | |||
}).then(done) | |||
}) | |||
|
|||
// #6903 | |||
it('should set the selectedIndex correctly in the new v-mode', done => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spelling: v-mode :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx 😄
gebilaoxiong
force-pushed
the
fix-select-active-index
branch
2 times, most recently
from
November 1, 2017 07:26
a8e28ac
to
fa56f64
Compare
gebilaoxiong
force-pushed
the
fix-select-active-index
branch
from
November 1, 2017 07:32
fa56f64
to
aa3a082
Compare
yyx990803
added a commit
that referenced
this pull request
Nov 3, 2017
lovelope
pushed a commit
to lovelope/vue
that referenced
this pull request
Feb 1, 2018
lovelope
pushed a commit
to lovelope/vue
that referenced
this pull request
Feb 1, 2018
f2009
pushed a commit
to f2009/vue
that referenced
this pull request
Jan 25, 2019
f2009
pushed a commit
to f2009/vue
that referenced
this pull request
Jan 25, 2019
aJean
pushed a commit
to aJean/vue
that referenced
this pull request
Aug 19, 2020
aJean
pushed a commit
to aJean/vue
that referenced
this pull request
Aug 19, 2020
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.
#6903
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: