-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple toasts with different positions take first position #438
Comments
I tried your "hack" @kurtcarpenter but it didn't work well. As you can see here if we specify the Does it mean that to use your "hack" we need to define the style for the new containerId? |
Can be corrected with two changes
|
disruptek
added a commit
to disruptek/toastr
that referenced
this issue
Mar 24, 2017
TimFerrell
added a commit
that referenced
this issue
Apr 11, 2017
fix for multiple toasts with different positions; closes #438
I think this is the same issue as "position no change" #386 Here's an example of the issue: https://codepen.io/grantiverson/pen/GGMKzV |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create a toast. While the first toast is visible, create a second toast with a different position- the second toast will be placed with the first, ignoring its own setting.
e.g.
results in
The library looks for a given container ID, which defaults to "toast-container". While it is possible to set this with an option, e.g.
{ containerId: "myContainer" }
, this is not well-documented behavior. Additionally, it is a major usability concern to force an extra, undocumented option in order to position correctly, i.e. achieve expected behavior.The text was updated successfully, but these errors were encountered: