Unable to show toast in a new position until all previous toasts disappear
See original GitHub issuetoastr.info('a', null, {
positionClass: 'toast-top-right'
});
toastr.info('a', null, {
positionClass: 'toast-bottom-left'
})
Second toast is shown in top right position
Issue Analytics
- State:
- Created 10 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Can I cancel previous Toast when I want to show an other ...
What I have done is to create a Toast wrapper, that contains a static reference to the last Toast displayed. When I need...
Read more >Toast - NativeBase
The Toast terminates itself when the close button is clicked or after a preset timeout — the default is 5 seconds. The component...
Read more >toast() API
You can dismiss all toasts at once, by leaving out the toastId . Dismiss all toasts at once. toast.dismiss();.
Read more >Toasts - Bootstrap
Push notifications to your visitors with a toast, a lightweight and easily customizable alert message. Toasts are lightweight notifications designed to mimic ...
Read more >The UX of notification toasts - Front-end developer in Nantes
Don't use an automatically fading toast if it carries information that absolutely can't be missed. The current account's billing information is ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is a single toast container object where all toasts live. For this to go to multiple areas it would need multiple containers.
However, the behavior you are seeing is correct and as designed. I decided that I did not want multiple toasts in multiple areas mostly for UX.
Don’t you find the API confusing then? It doesn’t reflect the ‘single-contairness’.