-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS - the page is being scrolled in background for tall modals #1956
Comments
I was able to reproduce this, but only a couple of times and it seems that it happens randomly. I can't come up with the steps to reproduce. |
This problem is so antique, it almost like unsolvable using pure JavaScript code and CSS. I think the problem you're experimenting with is the "iOS Safari Scrolling Issue". Sometimes the scroll freezes, sometimes it only scrolls the body element, like it attaches the highest DOM node, not the |
Hey! @limonte trying to reproduce this a four of times or more (iOS 14.2 beta) randomly in some browsers: Safari, Firefox and Chrome. I don't see any unexpected behavior, always scrolling is OK. |
Check this too @limonte |
Still reproducible (iOS 14.2) here: https://sweetalert2.github.io/ Reproducible if you try to scroll right after triggering the modal: |
iOS 14.6 (18F72) NOTE: ¿Will it be OK in this version? @limonte |
The issue is still happening in iOS 15. |
@limonte thanks for the update. |
This commit fixes a bug where you could scroll the background (page) when you reached the end of the alert.
I solved this issue for my own dialog plugin by using the following steps:
This solutions works for me on my iPhone the last two years without any issues. And I only do this fix on mobile where this issue exists. I hope it helps you fix it for iOS forever ;-) |
If you watch this video you will see after scrolling to the bottom the content in the background can be scrolled. Look at the top right hand corner for the darker scroll bar to move.
Originally posted by @wilecoyte78 in #1948 (comment)
The text was updated successfully, but these errors were encountered: