library overlay container duplicated (v3) #15949
Unanswered
SoftWebMike
asked this question in
Q&A
Replies: 2 comments
-
Pretty old answer but the concept is still the same: #4068 (comment) |
Beta Was this translation helpful? Give feedback.
0 replies
-
How does the answer change with the existence of createVuetify where there is no global instance? The library should reuse the app vuetify right? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have two vue repositories, both using vuetify (v3) beta:
What we are seeing is that when app initializes, it adds two DOM elements, both with the class "v-overlay-container". When we invoke a modal from the library that exposes a slot, it loads to overlay container A. Within that slot, we define an autocomplete within the app.
What we are seeing, is that when we interact with the autocomplete, the autocomplete options are rendered behind the modal. When we inspect the DOM, we can see that the autocomplete is not using the same overlay container as the modal, and thus the z-index is not being resolved.
Further investigation suggests that all components with overlay requirements within the library are loaded to the container, and those from the app are loaded to container B.
The questions here are:
Beta Was this translation helpful? Give feedback.
All reactions