Chaining modals and running modals in sequence has incorrect behaviour

[daattali]

Current behavior

These are a few interrelated bugs. I'll show three examples

1. When calling two modals one after another: only the second one shows.
2. When calling two modals, with the first one calling another modal in its promise: the modal in the promise gets shown immediately
3. When calling two modals, with each of them having another modal in its promise: the modal in the second one's promise gets shown

Expected behavior

I would expect to see the modals in the correct order. In the three cases described above:

1. Show the first modal, and only after it gets dismissed, show the second
2. Either show the first modal, then the one in its promise, and then the second one. Or the first one, then the second, then the one in the promise. It's up for debate what is the more correct behaviour, but the current behaviour is definitely incorrect
3. Similar logic to 2

Live demo !!! THIS FIELD IS REQUIRED !!!

All three code samples are in this pen: https://codepen.io/daattali/pen/mdYebqx

[limonte]

https://sweetalert2.github.io/recipe-gallery/queue-with-progress-steps.html

[daattali]

Using progress steps is a related feature that can achieve a similar result, but it's inherently a very different (and much more complex) syntax for a different usecase. There are cases when multiple popups might need to happen, in an unrelated manner where the different popups don't know about each other.

Example 1: imagine if the user clicks button A, then popup A is shown. If they click button B, popup B is shown. If they click button C, both popups are shown. It would lead to much cleaner and more intuitive code if C can simply call both A and B, rather than having to use completely different code.

Example 2: imagine that popup A happens on a schedule, and popup B is currently showing because of a user action. When A is triggered, it'll automatically take over B.

My reason for wanting this to be simpler is because I have a package in a different language (R) that brings sweetalert's functionality, and currently users can call shinyalert("one"); shinyalert("two") to see two successive popups. I care a lot about ease of use, and I believe that requiring end users to learn a completely different syntax and write a lot more code for doing something trivial is not the correct behaviour. The API should be as simple and clean to use, and the current way is great if you truly have "steps", but not for chaining modals.

[limonte]

async/await is the answer.