-
Notifications
You must be signed in to change notification settings - Fork 99
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
Vuetify compatibility #128
Comments
For that particular problem, add a |
@alfreema Could you further develop what to do? I have this in my HTML:
This in my typescript entrypoint:
Then MyComponent.vue:
|
I don't think v-dialog works well inside a web component, but if you want them to work at all you have to put:
in your HTML. Vuetify requires a div with data-app attached to it. See this answer for another example of the issue: https://stackoverflow.com/a/60990132/2957186 I suppose you could create it dynamically in javascript too, but I didn't try it. You'd do something like ...
but I went a different direction. I gave up on using v-dialog as it introduced a host of issues and I found that using a standard HTML
v-dialog is one of the only Vuetify components I really tussled with other than perhaps v-autocomplete. So far the rest of the components have worked quite well inside my web component. |
As with vue-custom-element, I'm having the same problem with getting Vuetify to working when the custom element is using shadowDOM.
vue-custom-element works fine when it's not using shadowDOM but it's not a bulletproof solution due to CSS conflicts when importing the web component onto 3rd party websites.
The error I get is the following:
Has anyone encountered the same issue and managed to get Vuetify to work with shadowDOM?
The text was updated successfully, but these errors were encountered: