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
And for this test I use a periodic dispatcher of toasts:
useEffect(()=>{letcounter=0;setInterval(()=>{toast(`No ${counter}. This is notification number: ${counter}`,{hideProgressBar: true});counter++;},1000);},[]);
When a toast is closed (regardless of method: user action/expiration time) and a new toast is added from a queue (imposed by the limit=3 prop) it feels like they do not respect the stacked property of ToastContainer
The text was updated successfully, but these errors were encountered:
ratasorin
changed the title
[Toasts Stack] Elements don't respect stacked property in ToastContainer
[Toasts Stack] Elements don't respect stacked layout in ToastContainerNov 14, 2024
ratasorin
changed the title
[Toasts Stack] Elements don't respect stacked layout in ToastContainer
[Bug] Elements don't respect stacked layout in ToastContainerNov 14, 2024
I would like to report a bug in the current implementation of the stacked toasts:
I have a
ToastContainer
with the following config:And for this test I use a periodic dispatcher of toasts:
The result is illustrated in the following video:
Here is also a codesandbox:
https://codesandbox.io/p/sandbox/gdp6cq
When a toast is closed (regardless of method: user action/expiration time) and a new toast is added from a queue (imposed by the
limit=3
prop) it feels like they do not respect thestacked
property of ToastContainerThe text was updated successfully, but these errors were encountered: