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
The Nuxt UI notification component is currently being created and added to the DOM even when no toast has been triggered. This behavior leads to unintended consequences due to the component's z-index:
The notification component occupies part of the screen unnecessarily.
It overlaps other elements on the page due to its z-index, potentially disrupting the user interface.
Expected Behavior
The notification component should only be created and added to the DOM when a toast is actually triggered.
Current Behavior
The notification component is always present in the DOM, regardless of whether a toast has been triggered or not.
Steps to Reproduce
Implement the Nuxt UI notification component in a project.
Inspect the DOM without triggering any toasts.
Observe that the notification component is present and has a z-index applied.
Additional Context
This issue affects the usability and performance of applications using the Nuxt UI notification component. Resolving it would improve both the user experience and the overall efficiency of the component.
Possible Solution
Consider implementing a conditional rendering approach where the notification component is only added to the DOM when it's actually needed (i.e., when a toast is triggered).
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Darwin
v22.3.0
3.13.1
3.13.1
2.9.7
[email protected]
-
compatibilityDate
,devtools
,modules
,plugins
,runtimeConfig
,i18n
@nuxt/[email protected]
,@nuxtjs/[email protected]
-
Version
v2.18.4
Reproduction
https://stackblitz.com/edit/nuxt-ui-jfdc58?file=app.vue,app.config.ts
Description
Description
The Nuxt UI notification component is currently being created and added to the DOM even when no toast has been triggered. This behavior leads to unintended consequences due to the component's z-index:
The notification component occupies part of the screen unnecessarily.
It overlaps other elements on the page due to its z-index, potentially disrupting the user interface.
Expected Behavior
The notification component should only be created and added to the DOM when a toast is actually triggered.
Current Behavior
The notification component is always present in the DOM, regardless of whether a toast has been triggered or not.
Steps to Reproduce
Additional Context
This issue affects the usability and performance of applications using the Nuxt UI notification component. Resolving it would improve both the user experience and the overall efficiency of the component.
Possible Solution
Consider implementing a conditional rendering approach where the notification component is only added to the DOM when it's actually needed (i.e., when a toast is triggered).
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: