Vuetify Version: 2.1.0
Last working version: 2.0.19
Vue Version: 2.6.10
Browsers: Chrome 77.0.3865.90
OS: Linux x86_64
v-model's value can be set to true from the start. This is helpful when globally registering components in Vue that are strictly for Dialog purposes. When a calling component activates the registered dialog component, I expect the dialog's v-model to be true from the start.
Dialog never appears.
https://codepen.io/nmummau/pen/oNvKYOB?editors=1010
As a work around, if set the dialog's v-model value to false to begin with... Then create a sleep() on the created() hook of the dialog component, and once that resolves set the v-model's value to true. Then the component appears!
I rolled back my project to use [email protected] and everything is back to a functional state. I'll wait to upgrade until this bug is fixed.
Temporary fix for this
```
.v-dialog__container {
display: unset;
}
Temporary fix for this
.v-dialog__container { display: unset; }
This didn't worked for me
is there any way which does not sets v-dialog on close to 'display:none" in v1.5
rather re-renders it so that vue life cycle methods can be used
Temporary fix for this
.v-dialog__container { display: unset; }This didn't worked for me
is there any way which does not sets v-dialog on close to 'display:none" in v1.5
rather re-renders it so that vue life cycle methods can be used
This bug is fixed and you do not need my workaround anymore. If you want life cycle events to fire, you must put a v-if on parent element and toggle it accordingly.
Most helpful comment
Temporary fix for this
```
.v-dialog__container {
display: unset;
}