-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[Dialog] Scrolling touchable content does not work on Safari Mobile #3755
Comments
I tried some workarounds and the only working solution that i came up with is a custom list item: JavaScript:
CSS:
I tried to make the ripple effect with
So I don't have the ripple at the moment. I hope somebody can come up with a fix or a better workaround. |
When the dialog pops up, it sets the background to
|
As far as I know, this is an issue of iOS Safari. I don't think that we can do much about it. |
Related to #8050 |
Fast fix
|
Problem Description
I'm having a scrollabale (don't think that it matters) page with an overlaying
Dialog
. TheDialog
contains aList
, which is also scrollable. TheList
element containsListItem
s andDivider
s. When I try to scroll the list, the item on which my finger is placed, is marked gray (selected). When moving the finger, the list does not scroll but the rest of the page, which is overlayed by the dialog, is pulled down. As you can see on the print screen, the page is pulled down like it can be done for refreshing. The annoying thing is, that sometimes it works as intended but most times the overlayed content is pulled down (don't know what the reason therefore is).Possible solution? http://www.two-legs.com/2012/07/html5-native-scrolling-on-iphone-ios5/Update: Looks like the list causes the problem. There is no problem when rendering only plain text in the dialog body.
Update 2: The problem might be caused by
onTouchTap
of theListItem
s. When using inactive content (i.e. removingonTouchTap
or disabling it using the propertydisabled: true
), scrolling works just fine.Versions
The text was updated successfully, but these errors were encountered: