Limon Monte

There's a drawer functionality: https://sweetalert2.github.io/recipe-gallery/sidebars-drawers.html But it's not mobile gesture friendly like https://github.com/emilkowalski/vaul is. I'll keep this issue open, need to think about if I need to improve the drawers...

Hey Mikael, From what I know about toasts and their a11y they shouldn't be dismissed by Esc. I read the related issue on the lossless-cut side, could you also share...

1. Docs don't seem to match the reality for Abode Spectrum: https://react-spectrum.adobe.com/react-spectrum/Toast.html 2. I still don't understand what'll happen with multiple material ui snackbars when Esc is pressed 3. That's...

Got you, I'll keep this issue opened, but can't promise that it'll be addressed. I'm still unsure about would this be right behavior for toasts or not.

Hey @ddev10d it's still undecided if this should be implemented or not, so no need for help atm, thanks!

I guess you're using Tailwind CSS v4. After some research I have to say: fuck Tailwind CSS v4 😆 what a nonsense for not-so-smart people like me. Maybe I'll revisit...

Thanks for reporting @pipob-mts I guess this would be fixed after I add CSS custom properties support: https://stackoverflow.com/a/3012987/1331425 Otherwise, the solution would be too JS and ugly 😄

:tada: This issue has been resolved in version 11.19.0 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/sweetalert2/v/11.19.0) - [GitHub release](https://github.com/sweetalert2/sweetalert2/releases/tag/v11.19.0) Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

```js pdfjsLib.GlobalWorkerOptions.workerSrc = 'https://mozilla.github.io/pdf.js/build/pdf.worker.mjs' // SweetAlert2 popup Swal.fire({ title: 'PDF Preview', html: '', width: 'auto', didOpen: async () => { const pdfUrl = 'https://pdfobject.com/pdf/sample.pdf' const loadingTask = pdfjsLib.getDocument(pdfUrl) const pdf...

> Maybe this new issue would be considered as a duplicate of this other issue. This is not a duplicate. The proposed here `minimumReleaseAge` is not the same as proposed...