Closed soetz closed 1 month ago
@soetz It looks like Vuetify is doing some internal overriding on how components render, or in this case if you are using it inside some of their components.
To fix this, pass the config prop with :config={ shadowDom: true }
which should resolve the issue.
Thanks @Jasenkoo, this looks like it works. I have one question though: this prop doesn’t actually use shadow DOM directly, right? It just changes how the datepicker renders to make it possible to use it in conjunction with the shadow DOM. Or did I get it wrong?
@soetz Yes, you are right, no additional changes are made, it just doesn't use slots to pre-calculate position.
Great, thanks again, and thanks for the great library.
Same bug with action-extra slot, thanks a lot for this project. @Jasenkoo
Describe the bug This bug seems very similar to #572. Using any Vuetify component in a VueDatePicker slot prints the error in the console and the datepicker menu doesn’t open.
Here are the errors that I get:
![Uncaught Error: [Vuetify] Could not find defaults instance
at injectDefaults (chunk-3SA2LMFG.js?v=6b41c1b1:1311:11)
at setup (chunk-3SA2LMFG.js?v=6b41c1b1:1127:24)
at callWithErrorHandling (chunk-PW74NBAW.js?v=6b41c1b1:1676:19)
at setupStatefulComponent (chunk-PW74NBAW.js?v=6b41c1b1:9137:25)
at setupComponent (chunk-PW74NBAW.js?v=6b41c1b1:9098:36)
at mountComponent (chunk-PW74NBAW.js?v=6b41c1b1:6526:7)
at processComponent (chunk-PW74NBAW.js?v=6b41c1b1:6492:9)
at patch (chunk-PW74NBAW.js?v=6b41c1b1:5961:11)
at mountChildren (chunk-PW74NBAW.js?v=6b41c1b1:6203:7)
at mountElement (chunk-PW74NBAW.js?v=6b41c1b1:6116:7)](https://github.com/user-attachments/assets/18ea4f81-9a5f-4a23-8b56-92626a66df52)
To Reproduce
Expected behavior The same as with v8: https://stackblitz.com/edit/vitejs-vite-vau6bq?file=src%2FApp.vue The menu opens and the Vuetify components are shown inside.
Desktop & mobile (please complete the following information):