Skip to content
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

[Bug Report][3.5.16] VSelect always jumps back to the first record when making multiple selections #19635

Assignees
Labels
C: VSelect VSelect T: bug Functionality that does not work as intended/expected T: regression Something that used to work but we broke
Milestone

Comments

@AndyBeat
Copy link

Environment

Vuetify Version: 3.5.16
Vue Version: 3.4.21
Browsers: Chrome 122.0.0.0
OS: Windows 10

Steps to reproduce

Choose item[Alabama], then item[Guam]

Expected Behavior

Same effect as Vuetify3.5.15 version

Actual Behavior

Jump to Alabama when choosing Guam

Reproduction Link

https://play.vuetifyjs.com/#...

Other comments

Affected by these 2 issues #19593 and #19574..

@KaelWD KaelWD added T: bug Functionality that does not work as intended/expected T: regression Something that used to work but we broke C: VSelect VSelect labels Apr 18, 2024
@KaelWD KaelWD added this to the v3.5.x milestone Apr 18, 2024
@yuwu9145 yuwu9145 self-assigned this Apr 18, 2024
@AndyBeat
Copy link
Author

@yuwu9145 You seem to have misunderstood what I meant. Instead of always scrolling to the last one, it will stay at the selected one, just like the version 3.5.15.
For example, select [Alabama], then [Guam], and then select [Colorado] instead of jumping back to [Guam], you stay in [Colorado].

@yuwu9145
Copy link
Member

yuwu9145 commented Apr 19, 2024

@AndyBeat Yes, the first fix d65d586 was wrong.

There is a new fix #19642 that makes sure stay at/scroll to "the last selected one". I plan to do more testing around this change over weekend to make sure it covers all scenarios

@yuwu9145 yuwu9145 reopened this Apr 19, 2024
@AndyBeat
Copy link
Author

@yuwu9145 OK, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment