-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
bug(sidenav): Scroll locking and jumpy for md-sidenav content on iOS (Safari) #5606
Comments
@YeomansIII this is a general problem of scrolling an element with A way to solve this issue is by listening to the |
On my end it is working 90% correctly. The only one case, when I run into issue with scrolling side-nav layout in ios, is when using dynamically added content:
|
Seeing same issue on iOS. I can click on the content, but it's not scrollable. Only when I click on the content (and on click) it jumps to their page, it becomes scrollable. Is there a workaround? I'll try the touchmove, but was wondering maybe there was a styling approach or an on init force this view so it works approach |
Hi, same issue here. Any clue @mmalerba ? |
I'm working on #6712 which will allow the sidenav to be put in fixed position mode, that way you can just let the body scroll naturally and not use overflow:auto and the fixed position sidenav will remain in place |
Hi @mmalerba ,
If I remove swiperight and swipeleft events, scroll is not blocked anymore. |
sidenav now supports fixed position mode, documentation was added in #7775 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug
What is the expected behavior?
Content inside md-sidenav-container should scroll smoothly all the time.
What is the current behavior?
Content inside md-sidenav-container can lock and disallow scrolling. This continues until the page is given time to sit without interaction.
Demonstration
What are the steps to reproduce?
This can be seen happening on the material.angular.io Components page on iOS in Safari.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: ^4.0.0
Material: beta.8
iOS 10, Safari
The text was updated successfully, but these errors were encountered: