We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Vuetify Version: 2.6.0 Last working version: 2.3.15 Vue Version: 2.6.11 Browsers: Firefox 94.0 OS: Linux x86_64
So this is a regression bug that was introduced when #12517 was fixed. When the array of autocomplete items contains a null item the error appears.
The autocomplete alternatives should render correctly.
Well it "crashes" on a NullPointer reference and the autocomplete becomes somewhat unusable.
https://codepen.io/billerby/pen/qBXwpPa
Quite a few users seems to have ran into this issue. See the comments in #12517
The text was updated successfully, but these errors were encountered:
Check that item. fixes vuetifyjs#14421
2528f14
Null items should not be added to list of unique items. fixes vuetify…
411dfc8
…js#14421
fix(VSelect): Do not keep null items when filtering duplicates
80905ea
resolves vuetifyjs#14421
fix(VSelect): Do not keep null items when filtering duplicates (#14464)
8fd3510
fixes #14421
KaelWD
Successfully merging a pull request may close this issue.
Environment
Vuetify Version: 2.6.0
Last working version: 2.3.15
Vue Version: 2.6.11
Browsers: Firefox 94.0
OS: Linux x86_64
Steps to reproduce
So this is a regression bug that was introduced when #12517 was fixed. When the array of autocomplete items contains a null item the error appears.
Expected Behavior
The autocomplete alternatives should render correctly.
Actual Behavior
Well it "crashes" on a NullPointer reference and the autocomplete becomes somewhat unusable.
Reproduction Link
https://codepen.io/billerby/pen/qBXwpPa
Other comments
Quite a few users seems to have ran into this issue. See the comments in #12517
The text was updated successfully, but these errors were encountered: