Fixes #48 and #46; A delay is no longer required #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whenever we create html content using js instead of shiny::insertUI and similar functions, we also need to bind/unbind accordingly. When 2 sweet alerts are fired back to back, swal service adds the second sweet alert to a queue, which is then opened when the first one closes. The problem arises because when swalservice.js opens the second swal, corresponding functions in shinyalert.js and shinyalert.r (I'm not 100% sure exactly when shiny does the binding) that are responsible for handling the bindings are not called.
We can fix this by adding a simple Shiny.bindAll whenever swalservice has to open a queued up swal in openNextSwal
This is a simple one liner fix that doesn't even modify the underlying sweetalert library. It only makes modifications to swalservice.js, which is a code snippet taken from this issue.