-
-
Notifications
You must be signed in to change notification settings - Fork 204
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 issues with snap points + modal=false (bg interact-able) + non-dismissable + scroll #349
Comments
What exactly is not working on iOS? |
the interactions were janky / broken on iOS with the above settings. When trying to close it was dragging the page instead, and also the bg stuff wasn't interactable. I was able to hack around it with:
and wrapping the drawer with
Next I'm trying to render a nested drawer / layered drawers with all those settings, really pushing your lib here 😆 |
Have you tried using
Could you create a reproducible example for me to take a look at? thanks in advance |
with modal={false} it does allow things to be interactive under it, but the dragging to close doesn't work properly on iOS with all the mentioned settings:
I'll get back to you with a good example |
I am encountering somewhat of the same problem and it's visible in the snap point example as well. When setting modal to The only workaround I am thinking is making the drawer scrollable with handle only. vaul-modal-false-issue.mp4 |
I have the same issue. My ideal case would be: When scrolling up within the drawer:
I think for this to work properly the library would need first class support for scrollable content. |
https://codesandbox.io/p/sandbox/bold-boyd-hhtxpk has a decent (though not perfect) example of what I'm trying to achieve with scrolling. |
Dragging when |
Hi,
could you please create an example with a drawer that:
for context, I'm trying to build a similar UI to apple maps. I'm able to get it working on chrome/desktop and tested with smaller windows, but it doesn't work on an iOS device or simulator.
Thank you
The text was updated successfully, but these errors were encountered: