You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Save and reload the codepen with your change
BUG: for some reason when the v-model's value is set to true from the start, the dialog does not render...
Expected Behavior
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.
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 vuetify@2.0.19 and everything is back to a functional state. I'll wait to upgrade until this bug is fixed.
The text was updated successfully, but these errors were encountered:
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 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.
Environment
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
Steps to reproduce
BUG: for some reason when the v-model's value is set to true from the start, the dialog does not render...
Expected Behavior
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.
Actual Behavior
Dialog never appears.
Reproduction Link
https://codepen.io/nmummau/pen/oNvKYOB?editors=1010
Other comments
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 vuetify@2.0.19 and everything is back to a functional state. I'll wait to upgrade until this bug is fixed.
The text was updated successfully, but these errors were encountered: