Skip to content
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

Connected CDK Overlays sometimes get positioned outside the viewport #8452

Closed
adamdport opened this issue Nov 15, 2017 · 2 comments
Closed

Comments

@adamdport
Copy link

adamdport commented Nov 15, 2017

Bug, feature request, or proposal:

Bug

What is the expected behavior?

If the connected component is narrower than the viewport, the CDK should never position beyond the bounds of the viewport. I can't think of when this would be desirable. The top left corner should be at least 0, and the bottom right corner should be at most the width/height of body.

What is the current behavior?

CDK overlays sometimes gets positioned such that the component attached to the overlay gets cut off.

What are the steps to reproduce?

http://plnkr.co/edit/qbivIGe33PpHY1ybd6ZR?p=preview

Good: good
Bad: bad

What is the use-case or motivation for changing an existing behavior?

Users should be able to see the entire overlay if there is room to display it. If the overlays have close buttons, it's possible that they could be inaccessible.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

5.0.0, 5.0.0, chrome

Is there anything else we should know?

@jelbourn
Copy link
Member

Tracking this via #6534, which will cover this issue

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants