Answer 1

It looks like part of the sweetalert library is making a cross origin request that is getting blocked by cross origin policy.

I would create it more from scratch so the problem isn't nested deep in a third party library that I can't fix. Whether you blame the library or not, the inability to edit the code is an impediment if you don't quickly find a work around.

Below are some of the troubleshooting details I found.

In Google Chrome developer tools, my JavaScript console lists:
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://www.youtube.com/embed/X2OUNePV-6o with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.
Image (async)
f @ VM7 sweetalert.min.js:1
d @ VM7 sweetalert.min.js:1
e.initModalContent @ VM7 sweetalert.min.js:1
e.init @ VM7 sweetalert.min.js:1
(anonymous) @ VM7 sweetalert.min.js:1
s @ VM7 sweetalert.min.js:1
(anonymous) @ solocode.azurewebsites.net/:1
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://www.youtube.com/embed/X2OUNePV-6o with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.

In Microsoft Edge, I get a similar message:
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://www.youtube.com/embed/X2OUNePV-6o with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.
Image (async)
f @ sweetalert.min.js:1
d @ sweetalert.min.js:1
e.initModalContent @ sweetalert.min.js:1
e.init @ sweetalert.min.js:1
(anonymous) @ sweetalert.min.js:1
s @ sweetalert.min.js:1
(anonymous) @ (index):1