-
Notifications
You must be signed in to change notification settings - Fork 98
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
[Bug] Backdrop not removed when 2 notifications with same timeout #57
Comments
I have the same problem when I call a notification with the backdrop enabled, the following notification calls also work with the backdrop enabled, ignoring the configuration settings. Does not help even a forced call to vm.$snotify.setDefaults(config: SnotifyDefaults) |
Hello, As I had many problems with this bug, I tweaked your package by adding an initTime to each toast (timestamp divided by 100 and rounded for precision purposes): For some reason I had to change the template to HTH you finding a way to fix this. Thank you again! |
I am having a similar issue with the backdrop not being removed. I found this in the JS file: Any news on when this will be fixed? Does anyone know a work around, at the moment the backdrop dosesnt get removed which then prevents users being able to access the form behind the backdrop |
Basically, my fix is explained in my previous post. But here is what I did for now in
|
Thank you, will have a look at trying this. Its better than my work around :) |
Why you don't create that PR ? This is one of the solution |
Hello,
First of all, thank you for this package. I noticed that when you programatically call 2 notifications with the same timeout, the backdrop is not removed. Do you have any solution for this problem?
Thank you!
The text was updated successfully, but these errors were encountered: