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
For what version of Nuxt UI are you asking this question?
v3-alpha
Description
I have labelled it as a question, it could be a bug, but I will let you decide.
It seems like the Toast component has not a high enough z-index to be above everything. (Should it?)
I took notice when using the Drawer but I guess (not tested) it applies i.e. to the Slideover as well. The Toast Message has appeared under the Drawer so the user cannot see it. Imo the toast should be above everything.
Both Drawer and Toast have a z-index of 100 if I saw that correctly. I tried to change the z-index inside the Toastproperties but that doesn't seem to have an effect.
I worked around and just put the Toast in another corner so the user can see it but still is unable to interact with it because the Drawer will close if he clicks outside.
But maybe there is another way to deal with this?
The text was updated successfully, but these errors were encountered:
For what version of Nuxt UI are you asking this question?
v3-alpha
Description
I have labelled it as a question, it could be a bug, but I will let you decide.
It seems like the Toast component has not a high enough z-index to be above everything. (Should it?)
I took notice when using the
Drawer
but I guess (not tested) it applies i.e. to theSlideover
as well. The Toast Message has appeared under the Drawer so the user cannot see it. Imo the toast should be above everything.Both
Drawer
andToast
have a z-index of 100 if I saw that correctly. I tried to change the z-index inside the Toastproperties but that doesn't seem to have an effect.I worked around and just put the Toast in another corner so the user can see it but still is unable to interact with it because the
Drawer
will close if he clicks outside.But maybe there is another way to deal with this?
The text was updated successfully, but these errors were encountered: