Vuetify Version: 3.5.15
Last working version: 3.5.15
Vue Version: 3.4.21
Browsers: Chrome 123.0.0.0
OS: Mac OS 10.15.7, Windows
Steps to reproduce
Choose one date from "Second DatePicker" which is using in a shadowRoot. For example, Apr.30, it works!
2.Let's change the Second DatePicker again, If you click the those icons to switch the month or year, the menu will be quickly closed even if using the :close-on-content-click="false" in v-menu.
The operations of the above 1 and 2 steps can be successfully completed in the first DatePicker
Expected Behavior
v-menu won't be closed in second time popup if it using in the shadowRoot
Actual Behavior
v-menu was be closed when using in shadowRoot even through using close-on-content-click="false"
Hi, Vuetify team, since Front-end micro app more and more popular, this could be a common problem, so I did in-depth research about this issue, and we have a result.
The root cause is that the v-clickout directive using the wrong lifecyle, so, I want to try to fix this issue.
Environment
Vuetify Version: 3.5.15 Last working version: 3.5.15 Vue Version: 3.4.21 Browsers: Chrome 123.0.0.0 OS: Mac OS 10.15.7, Windows
Steps to reproduce
Choose one date from "Second DatePicker" which is using in a shadowRoot. For example, Apr.30, it works! 2.Let's change the Second DatePicker again, If you click the those icons to switch the month or year, the menu will be quickly closed even if using the :close-on-content-click="false" in v-menu.
The operations of the above 1 and 2 steps can be successfully completed in the first DatePicker
Expected Behavior
v-menu won't be closed in second time popup if it using in the shadowRoot
Actual Behavior
v-menu was be closed when using in shadowRoot even through using close-on-content-click="false"
Reproduction Link
https://play.vuetifyjs.com/#...
Other comments
Hi, Vuetify team, since Front-end micro app more and more popular, this could be a common problem, so I did in-depth research about this issue, and we have a result. The root cause is that the v-clickout directive using the wrong lifecyle, so, I want to try to fix this issue.