-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Vertical positioning of flexible connected overlay on mobile #13614
Comments
Can you provide a reproduction in StackBlitz. This will help us to investigate the issue you are seeing. |
Thanks for your answer @josephperrott. I made a example for you: https://stackblitz.com/edit/angular-jh76xz You have to open the example on a real mobile device. You will find three touchable elements on the page. The first and the last element work as expected, but hen you touch the second element you will see that the position of the opened overlay is not correct |
Is there any progress? |
Anything happened here? |
Bug still exists. Is there any progress on this Bug? |
We are having the exact same issue. Curious to know if there is a workaround or solution in sight? |
Hello! I proposed a solution to this problem here #28425 |
@crisbeto @andrewseguin could you look at mine PR #28425 ? |
Bug, feature request, or proposal:
Bug
What is the expected behavior?
Flexible connected overlays are positioned correct even if the user is scrolling
What is the current behavior?
Scrolling affects the vertical positioning of the overlay. The overlay is positioned to low.
What are the steps to reproduce?
Scroll down a page on a mobile device (not to the end of the page, but somewhere in the middle) and then open the flexible connected overlay. The overlay seems to be positioned to low.
Example desktop:
Example mobile:
Configuration of the overlay:
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
@angular/core: 6.1.0
@angular/material: 6.4.7
@angular/cdk: 7.0.0-rc.1
typescript: 2.7.2
The text was updated successfully, but these errors were encountered: