-
Notifications
You must be signed in to change notification settings - Fork 92
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
Issue with alert closing #2
Comments
Hello, ngsweetalert2 is just an integration for SweetAlert2, we do not perform any DOM operations in this library, that's only "wrapping logic". There may be a bug in the upstream library. Please open an issue in their repository, mentioning the browser you are using, and providing a jsfiddle to reproduce the bug. |
I understand. Strangely it works by using SweetAlert. What happens is that when using ngsweetalert, the swal2-container created is not removed when closing the alert. I'm going to adapt Sweetalert to my project. Thank you. |
Oh, then it changes everything. Maybe your setup was incomplete, but I can't really find an explanation for such a bug. NgSweetalert2 calls sweetalert2 directly and does not perform any other DOM operation. If you could provide the minimal boilerplate for reproducing the bug, I would be happy to investigate further, and I'll reopen the issue. |
I'm also having this issue, maybe because I'm using flexbox heavily (bootstrap v4). I tried including limonte/sweetalert2 scss styles to my project, doesn't seems to solve the problem. |
Hi... I'm having trouble using sweetAlert. When it is closed, swal2-container blocks the other components of the screen.
The text was updated successfully, but these errors were encountered: