-
-
Notifications
You must be signed in to change notification settings - Fork 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
[Bug Report][3.6.11] VExpansionPanels value prop not working #20109
Closed
Icebreaker83 opened this issue
Jul 5, 2024
· 6 comments
· Fixed by Enterprise-CMCS/cmcs-eregulations#1413 · 4 remaining pull requests
Closed
[Bug Report][3.6.11] VExpansionPanels value prop not working #20109
Icebreaker83 opened this issue
Jul 5, 2024
· 6 comments
· Fixed by Enterprise-CMCS/cmcs-eregulations#1413 · 4 remaining pull requests
Labels
Comments
v-model is |
Panels are not open by default, because you don't set a value for <template>
<v-app>
<v-container>
<v-expansion-panels :model-value="[0]">
<v-expansion-panel :value="0"> <-- this is point
<template #title>
<h4>Some title</h4>
</template>
<template #text>
<h4>Content</h4>
</template>
</v-expansion-panel>
</v-expansion-panels>
</v-container>
</v-app>
</template>
<script setup>
import { ref } from 'vue'
const expand = ref([0])
</script> |
@nguyentranchung Makes sense. Thanks! |
This issue can be closed |
The default value is the index, the problem here was just using value instead of model-value. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Vuetify Version: 3.6.11
Vue Version: 3.4.31
Browsers: Chrome 126.0.0.0
OS: Windows 10
Steps to reproduce
Expected Behavior
Panels with indexes that are in value prop should be opened by default
Actual Behavior
Panels are not open by default.
Reproduction Link
https://play.vuetifyjs.com/#...
Other comments
I've tried with
:value="[0]"
,:value="0"
, on v-expansion-panels and on v-expansion-panel.Currently only way of getting the expansion panel open by default is through v-model.
The text was updated successfully, but these errors were encountered: