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
When we set maxToasts = 1 we can only see 1 toast at the same time. However, some of them have quite long expiration time (will say, 7-8 seconds). And when some other toast triggered, it comes to queue and waits untill first one will disappear. However, that can be not user friendly, especially when user clicks some button and about 3-4 toasts are coming to queue. Then, next 30 seconds some toasts will change each other, user can even forget what caused that toasts.
demo.mp4
It will be good to have some ability to say vue-toastification, that new toast should make old one dismissed (if it's still on screen), so that user will see the most recent message.
You could do some dismissOldOnNew flag, which can be true or false. If it's true, then new toast will make old one dismissed (or the oldest one in queue in case when maxToasts > 1). If it's false, then behaviour stays the same as now.
The text was updated successfully, but these errors were encountered:
We need
dismissOldOnNew
flagWhen we set
maxToasts = 1
we can only see 1 toast at the same time. However, some of them have quite long expiration time (will say, 7-8 seconds). And when some other toast triggered, it comes to queue and waits untill first one will disappear. However, that can be not user friendly, especially when user clicks some button and about 3-4 toasts are coming to queue. Then, next 30 seconds some toasts will change each other, user can even forget what caused that toasts.demo.mp4
It will be good to have some ability to say vue-toastification, that new toast should make old one dismissed (if it's still on screen), so that user will see the most recent message.
You could do some
dismissOldOnNew
flag, which can be true or false. If it's true, then new toast will make old one dismissed (or the oldest one in queue in case whenmaxToasts > 1
). If it's false, then behaviour stays the same as now.The text was updated successfully, but these errors were encountered: