Uppy and SweetAlert2 bug

[epexa]

If use SweetAlert2 then there is a conflict with Uppy.

When the SweetAlert2 message is displayed and any button is pressed, the Uppy Dashboard is shown.

Live example:
https://gist.githack.com/epexa/110e28db117bed6a9b1ce8df6a2e7cd3/raw/4f503c7fc7dd244b62a46e8241d883abbf49ccae/uppy_sweetalert2_bug.html

[arturi]

Hi! Thanks for reporting. This looks a bug indeed, but it’s yet mysterious to me, how it can occur, when Uppy instance is isolated and SweetAlert2 doesn’t know about it.

One thought is browser history API, which we use for the browserBackButtonClose option, but it’s off by default.

[epexa]

@arturi Hi!

I was helped with the parameter change the "target".

Example:

target: '#uppy',

Live example:
https://gist.githack.com/epexa/1fe999461dd3f8784f420530892f77f5/raw/37a8393ebf368c0272bf469f13a9676d676f67cc/uppy_sweetalert2_bug_fix.html

[lakesare]

It's a bug within SweetAlert2, that removes all aria-hiddens from the direct children of the body, and we depend on the aria-hidden attribute in order to hide our modal: https://github.com/sweetalert2/sweetalert2/blob/60dd1e7634fecb23d397041fab8fab3b37ed75f4/src/utils/aria.js#L24.

[lakesare]

Setting target: '#uppy', helps, because it makes uppy instance not be a direct child of a body.
I posted it as a bug to sweetalert2: sweetalert2/sweetalert2#1648.