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
By default the notification seem to have functionality that allows them to stay on the screen while hovered. Is there a way to disable this? The reason is that I quickly found some edge cases where the notifications get stuck on the screen if the browser window loses focus, and I'm not sure it's easily fixable (because the mouseleave event probably doesn't trigger even when the window is activated again, unless you actually hover over the notification again)
I would rather not deal with this complexity, especially considering the notifications don't have a dismiss button by default, so end user might get into a situation where they don't understand why the notification stays on the screen.
Would it be possible to add something like pauseOnHover: boolean to disable the behavior and have the notifications always close at exactly the duration?
PS. Although a different issue, it would be nice to have a built-in "X" button to dismiss notifications, like svelte-notifications has.
The text was updated successfully, but these errors were encountered:
Hi guys, I had the same issue with the toast getting stuck on mobile, I was able to work around it by using.
the only issue with this is being able to click through the toast.
By default the notification seem to have functionality that allows them to stay on the screen while hovered. Is there a way to disable this? The reason is that I quickly found some edge cases where the notifications get stuck on the screen if the browser window loses focus, and I'm not sure it's easily fixable (because the
mouseleave
event probably doesn't trigger even when the window is activated again, unless you actually hover over the notification again)I would rather not deal with this complexity, especially considering the notifications don't have a dismiss button by default, so end user might get into a situation where they don't understand why the notification stays on the screen.
Would it be possible to add something like
pauseOnHover: boolean
to disable the behavior and have the notifications always close at exactly theduration
?PS. Although a different issue, it would be nice to have a built-in "X" button to dismiss notifications, like svelte-notifications has.
The text was updated successfully, but these errors were encountered: